This is my second self-hosted project. If you still remember me, I am the one who created Uptime Kuma, and I had posted here 2 years ago.
After joining this subreddit, I somehow fell into love with this community and also started enjoying using docker-compose to manage my containers.
However, I always interacted with docker-compose using the CLI only, as I couldn't find a web app that focuses on docker-compose management. Although Portainer has the ability to do that, it do not display any progress during "docker-compose up or pull" unfortunately, which makes me prefer to use the CLI.
So this time I tried to create my own stack-oriented manager to manage my compose.yaml files.
- Manage docker compose.yaml files
- Interactive compose.yaml editor
- Interactive web terminal
- The UI/UX is very similar to Uptime Kuma
It is really fully focused on docker compose, so please don't expect to manage a single container.
Don't forget to ⭐ the project on GitHub if you love it!
A little update for Uptime Kuma:
Uptime Kuma reached over 40,000 ⭐ on GitHub and over 48,000,000 pulls on Docker Hub!!! It is a big gift for me, thank you everyone! Uptime Kuma V2 is still under development, stay tuned!
I'm relatively new to the Docker "scene" and this looks like a really cool and simple way to manage the containers. (Looks easier than Portainer which I think is more business orientated)
Not sure if I'm missing a feature though - I already have a folder "docker" with sub folders for each container. Each container sub-folder contains a docker-compose.yml file
Is dockge able to automatically scan, import and give the option to deploy these containers?
If so, how do I do that?
I have the dockge stacks folder to be my top-level "docker" folder
Is there any possible consideration to having nested stacks? I currently have different compose structures nested together which I like for grouping purposes and I imagine it should / might be a nice enhancement to this application.
Great project! Any chance to make it use with a stack already deployed? I've got folder structure like something/docker/container-name/docker-compose.yml with relevant volumes mapped inside specific folders in the same level as docker-compose.yml
One thing I do not like about Portainer is that he sees stacks created outside of it, but it got very limited functionalities with them.
I just don't want to recreate/move all my services. Ain't broke, don't fix philosophy, just me being lazy
Uptime Kuma is awesome. I just gave it a go yesterday to monitor an upgrade at my work and loving it. Thank you. Will check out Dockge... How does one pronounce it, btw?
Would be nice to have to option to specify a .env file instead of explicitly writing all env vars. I like to have them in a seperate file for specific containers.
Would be nice to have a section to add labels, for us Traefik users out there.
Other than that looks great, I’ll definitely use it. Good job!!
yes please, base url support and mobile friendly UI , some time i just need to start/stop container through mobile and Portainer in mobile is terrible 😣
Great project, I love the idea. It would be even greater if you could manage images, like in Portainer for example (My use case: deleting unused images). The same question applies to the topic of volumes. Is it possible to integrate other Docker repositories as well? For Security reason it could be nice to use 2FA or Passkeys. :)
Looks great, unfortunately i’m running on docker swarm.
Hope it’ll support that somewhere in the future so i can use it. As i’m a great fan of uptime kuma and use it for work and private.
Question: Once I’ve used dockge to create multiple containers the yaml is nicely organised as separate compose files in the subfolder. Is it possible to use docker compose command to recursively up -d them all at once from the shell without having to manually specify the file names? It doesn’t support wildcards afaik?
I use portainer, how do I import my stacks? On the github you said to move them to a folder, so I guess the question is where do I even find them
I have about 40 stacks, do you expect me to create 40 folders and copy each compose file in its relevant folder? Is there an import/export feature (could it exist?) because that's one of the things I wish to have in portainer, some sort of backup for the stacks only.
Support Dockerfile and build
Yes! I'm existed to see what you do with that one.
Docked in, and loaded up! Quickly renamed my old docker-compose.yml to compose.yaml with this script running in my ‘compose’ folder of folders.
Pure beauty!
Thank you for making something not overly configurable, and something that just works.
This is now my new manager over SSH’ing in over tailscale, and trying to find new SSH apps every other week for my iPhone/Mac.
Literally hours saved.
A feature that would be nice to have is default settings for compose files. If I want to map user permissions, or map my media folder that is always going to be on my *arrrrrrrrr containers, that would be suuuper legit.
I’m gonna poke through the source once I get time to myself and see what I can come up with.
The quality of your work is amazing, and I genuinely thank you for allowing me now to setup/manage my containers while sitting on the toilet.
What would be great is integration with github or other source code management system. Also if you do this would be great to track/show version that is running.
looking good! Not sure if this is the direction you're looking to go with this project, but I'd love to see a docker compose stack manager that integrated a simple snapshot / backup system. My current situation (with Portainer) when I kludge something up is to either hope I can reconfigure things back they way they were, or revert my entire VM to an earlier state. I'd love to be able to revert a single stack in a few clicks (extra love if the solution used ZFS :). Related features might be simple one-file backup of a stack, or ability to easily migrate a stack from one host to another.
As a newb to docker and as someone who hasn't fully gelled with it this looks perfect. Seems it is doing exactly what I'm trying to do in the command line with the folder structures. Perfect timing as yesterday I completely lost the plot with my docker installation!
It has certainly helped me get my head round docker. I don't have to remember what folder I left that compose file in or what that command was. Because of using Dockge I now get the correlation between the command line and compose files (although I still hate languages that rely on whitespace/indenting but that's another rant for another day lol).
I really like the clean simplicity of this (and Uptime Kuma). Couple of things I think would be handy, some shortcuts or snippets for the console, rather than having to try and remember all the prune commands etc could have some custom one click buttons to do it (or maybe chain the commands like docker system prune -a && docker volume prune -a etc?
Are you integrating Telegram with this again? Obviously we can monitor the containers with UK but I was thinking of an alert if there's an update available if we can add some update check?
Absolutely lovely interface though, really glad this came along. Thank you!
Looks really good and I moved a few of the once I have into dockge.
Works great.
One suggestion.
Add Down and Up buttons as well.
Just stopping a container does not always work when you upgrade them. All depending on volumes and configuration of the stack