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
Comment on DockGE released 1.5.0
darkknight@discuss.online 4 days ago
I used this for a bit. Can you import existing stacks yet? That was my missing feature.
Nibodhika@lemmy.world 3 days ago
lka1988@lemmy.dbzer0.com 4 days ago
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.darkknight@discuss.online 4 days 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 4 days 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 4 days 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.