​

https://preview.redd.it/ra343yd71xzb1.png?width=1903&format=png&auto=webp&s=c28993a7b5a6ebe2d09b0d08896190e8e3349e0f

GitHub: https://github.com/louislam/dockge

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

A short introduction video: https://youtu.be/AWAlOQeNpgU?t=48

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!

​

  • iwangbowen@alien.topBEnglish
    1·
    1 year ago

    Great job 👍 Can you tell me how you achieve interactive yml editor and web terminal

  • Reasonable-Ladder300@alien.topBEnglish
    1·
    1 year ago

    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.

  • arghdubya@alien.topBEnglish
    1·
    1 year ago

    I’m finally ‘really’ getting into Docker because of this easy-to-understand helper app.

    Portainer, etc have too much going on and is wildly overkill for single instance hosts.

    Basic image management/info would be a nice addition.

    Great work!

  • markhaines@alien.topBEnglish
    1·
    1 year ago

    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?

  • brypie@alien.topBEnglish
    1·
    1 year ago

    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

    TIA

  • qwacko@alien.topBEnglish
    1·
    1 year ago

    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.

  • gnappoforever@alien.topBEnglish
    1·
    1 year ago

    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