​

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!

​

  • Wastelland_9995@alien.topBEnglish
    1·
    10 months ago

    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. :)

    I will eagerly follow the development.

    • MalcolmY@alien.topBEnglish
      1·
      10 months ago

      Compose is the best thing for me noobs like me when paired with portainer. Easy peasy.

  • goodtimtim@alien.topBEnglish
    1·
    10 months ago

    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.

    • louislamlam@alien.topOPBEnglish
      1·
      10 months ago

      Haven’t implemented upload function yet, you need to upload your .env files manually via SFTP.

  • tech2but1@alien.topBEnglish
    1·
    10 months ago

    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!

  • pierrebjarnfelt@alien.topBEnglish
    1·
    10 months ago

    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

  • PovilasID@alien.topBEnglish
    1·
    10 months ago

    This is cute but I have to be honest I prefer using VS code with SSH and docker plugins for managing compose files.

  • qwacko@alien.topBEnglish
    1·
    10 months 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·
    10 months 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