Thank you for posting it again.

DB Tech have made a video about Dockge, he explained my idea so well. https://www.youtube.com/watch?v=E805XcbTzgY

My previous post have also explained why I made this: https://www.reddit.com/r/selfhosted/comments/17tkq79/dockge_a_fancy_easytouse_selfhosted_docker/

Love how this looks, could definitely see myself moving from Portainer since I don’t use the majority of its features.

Though having to move all my stacks around is a bit of an annoyance. I have them split into their own folders to keep things tidier: Wonder if you could watch multiple folders in this too, rather than moving them all into Dockge’s folders.

I tried this out last and ended up going back to portainer. It’s a problem I could fix, but I didn’t want my services down for that long. All of my services are in 3 different compose files. I started up my stacks using dockge and it put each stack on it’s own network (that it created).

If I put all my containers in one compose file I suppose it would work.

My problem with portainer is that, if I deploy a stack (compose) via docker compose cli, it has limited control inside portainer. Is this the same? Or does this play nicely with compose files deployed outside of it?

This is interesting. I’m moving over my server from unraid to a clustered proxmox and was looking for something to handle my containers in a simple way, everyone kept recommending portainer and I hated it since it’s so bloated and somehow still missing features that I actually wanted. I ended starting to develop my own system for this but even more barebones in that it’s just a cli tool that will download all the unraid repos and allow you to search for an application and/or the author and use that to generate a docker compose file for you from those templates. I’m very used to the unraid App Store so it lets me easily keep things similar to how I already have it. It’s a WIP but it works and I just add features as I need them.

If I found this a couple of months ago though then I would have probably used this instead.

I have a folder called /docker-containers where I store all my compose files each on it’s folder, so if I want to run this manager with my already running containers, then I will need to point my current folder as:

home/name/docker-containers=/opt/stacks

is that right?

this looks great hopefully we can have the widget for Homepage dashboard!

Looks promising but like many others I need the ability to manage multiple hosts. That said I suppose there’s no reason you can’t spin up multiple instances, one on each host.

looks great

Spun this up last week. Love it. Simple, slick interface and easy to understand principles. Like being able to see what’s going on (or going wrong) as I deploy a stack. I know it’s in as a feature request already, because multi-node would make it the single pane solution for all my docker stuff.

Shout-out to /u/louislamlam it’s a great project!!

I will give it a try. I don’t like the fact of Portainer kidnapping my compose files. I want them plaintext on my drive, so I can backup them with regular tools.