https://github.com/arshamalh/dockeroller
A cool ChatOps Cli tool for connecting your docker engine to a telegram bot
https://github.com/arshamalh/dockeroller
chatops docker
Last synced: 5 months ago
JSON representation
A cool ChatOps Cli tool for connecting your docker engine to a telegram bot
- Host: GitHub
- URL: https://github.com/arshamalh/dockeroller
- Owner: arshamalh
- License: mit
- Created: 2022-09-05T12:52:20.000Z (almost 4 years ago)
- Default Branch: main
- Last Pushed: 2024-05-17T20:08:29.000Z (about 2 years ago)
- Last Synced: 2024-05-17T20:24:43.740Z (about 2 years ago)
- Topics: chatops, docker
- Language: Go
- Homepage:
- Size: 412 KB
- Stars: 26
- Watchers: 1
- Forks: 2
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Dockeroller 🐳
Dockeroller (docker controller) is an open-source project giving you the power to control your docker daemon through Telegram, it was made for fun and personal use, but it appears to have many real-world use cases and it is a part of ChatOps world!
> [!IMPORTANT]
> Dockeroller is made to run self-hosted, so WE WON'T ACCESS or STORE ANY OF YOUR DATA in any terms.
> [!CAUTION]
> Dockeroller is in Alpha phase and not yet production-ready
## How to use
First make sure you installed go version 1.19 or above then run:
````bash
go install github.com/arshamalh/dockeroller@main
````
Then you should make a bot (it's name and username doesn't matter) with [bot father](https://t.me/BotFather), copy its `token`, then you can run the CLI using:
```bash
dockeroller start --token ""
```
And now your docker daemon is accessible thorough your Telegram bot.
## Security
There is no security concerns as long as you keep your telegram account safe, and Whitelist known ids:
```bash
dockeroller start -w 22,33,44
```
Dockeroller will return your ChatID when you message it in an UnAuthorized state, then you can whitelist it.
We will also add a password mechanism soon.
## Features
- [x] Containers
- [x] List
- [x] Start
- [x] Stop
- [x] Live logs
- [x] Live stats
- [x] Remove
- [x] Rename
- [ ] Images
- [x] List
- [x] Remove
- [x] Tagging
## Note for developers and contributors
We cache containers and images list, and update this cache after "next, back, list, final rename, final remove" but we don't update this cache after "remove form buttons clicking", because we don't want you to face another container after clicking to "Force: false" button.
## Some Screen Shots
