Features:
- Manage
compose.yaml- Create/Edit/Start/Stop/Restart/Delete
- Update Docker Images
- Interactive Editor for
compose.yaml - Interactive Web Terminal
- Reactive
- Everything is just responsive. Progress (Pull/Up/Down) and terminal output are in real-time
- Easy-to-use & fancy UI
- If you love Uptime Kuma’s UI/UX, you will love this one too
- Convert
docker run ...commands intocompose.yaml - File based structure
- Dockge won’t kidnap your compose files, they are stored on your drive as usual. You can interact with them using normal
docker composecommands
- Dockge won’t kidnap your compose files, they are stored on your drive as usual. You can interact with them using normal
Dockge won’t kidnap your compose files, they are stored on your drive as usual. You can interact with them using normal docker compose commands
FUCK. YES.
This sounds like exactly what I have been looking for.
Finally! Goodbye Portainer!
Not sure this would entirely replace portainer for me since that manages multiple machines, but I am keen to play with this
This was my first thought as well. This isn’t a replacement for portainer agents on mulitple docker hosts, hopefully that’s something that is doable in the future.
I ditched portainer earlier this year to use the command line only, and don’t miss it at all. If you’re only using docker compose, I really don’t see the point of it.
The CLI is just fine. But a Dashboard can give you a much better and faster overview of everything. (Color highlighting and so on)
What’s wrong with Portainer?
- UI, just too many annoyances. Fkr example the cut off unhelpfull error messages
- compose files, like this project calls it are taken hostage by portainer
- git, while you can use a repository there is no comfortable way to test out changes and commit them to git. Would portainer use a sinple file structure for compose files that would not be a problem
- Ads, they try to promote there business version via the UI.
I could close my eyes to all of those, but the issue that pisses me off the most is that often enough Portainer just forgets which stacks it has ownership over, forcing you to delete the whole stack, dig up the old compose from its files, and create it again
This is also by the author of Uptime Kuma, which explains the similarity in UI.
I saw the logo and thought it looked TOO familiar
I’ll definitely be checking this out, thanks for the link
Is it a replacement for Unraid docker compose plugin?
Wow! This is beautiful!
