If the compose.yml can be moved to a place where Dockge is configured to look, then yes. Normally it’s configured to look in /opt/stacks/, but that can be changed.
Comment on DockGE released 1.5.0
darkknight@discuss.online 1 year ago
I used this for a bit. Can you import existing stacks yet? That was my missing feature.
lka1988@lemmy.dbzer0.com 1 year ago
darkknight@discuss.online 1 year ago
I just updated my dockge container, you still have to start compose files from dockge in order to manage them. Which requires copy/pasting compose files into dockge. If you have more than 2-3 compose files, this is a pia. To me, that’s not an import.
lka1988@lemmy.dbzer0.com 1 year ago
Dockge doesn’t really work like that. It works alongside Docker, the only thing it asks is that you point it to where your stacks are located. Like I said, that normally is set to
/opt/stacks/, but it’s not set in stone.darkknight@discuss.online 1 year ago
Thanks for the info, that’s definitely not how it’s working on my system, so I have something setup wrong. That explains my confusion.
Nibodhika@lemmy.world 1 year ago
You don’t need to, as long as our stack is all in one folder you just point it to that folder and it will work