Comment on Server and infrastructure building for me, a dummy
klangcola@reddthat.com 15 hours agoI had never heard of dockge before, but this sounds like the killer feature for me:
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 compose commands
Does that mean I can just point it at my existing docker compose files?
My current layout is a folder for each service/stack , which contains docker-compose.yaml + data-folders etc for the service. docker-compose and related config files are versioned in git.
I have portainer, but rarely use it , and won’t let it manage the configuration, because that interfered with versioning the config in git.
Does that mean I can just point it at my existing docker compose files?
You add the compose via the DockGE UI, it then creates the necessary files and folders in /opt/stacks/. Not sure whether it works the other way around: to create the folder, copy the compose file in there, and see if it is recognized.
I’ve been using it for over a year, works very smooth.
Do you version your compose files in git? If so, how does that work with the dockGE workflow?
No, I don’t, I only back up /opt/stacks to borgbase. I imagine it should be possible, but it might depend on how the projects are arranged in git. Monorepo might give trouble, but separate repo’s might work.
Seefoo@lemmy.world 9 hours ago
I tried out Komodo, but gave up on it. I looked at dockge after, but opted not to try it out. I prefer the IaaC setup with my compose in a repo for versioning and rollback. And while I think you can probably combine the two, komodo was getting in the way most of the time. I centered around secrets management and generating those secrets at run time.
That said, I feel like if I expand beyond a single server I may go back to one of these tools