Comment on DockGE released 1.5.0
lka1988@lemmy.dbzer0.com 1 week agoIf 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
lka1988@lemmy.dbzer0.com 1 week agoIf 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 1 week 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 week 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 week 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.
lka1988@lemmy.dbzer0.com 1 week ago
Let us know if you run into more snags! I’m happy to try to help out. I also revised my comment above several times last night and this morning as I was really tired and kept forgetting details 😅
The other thing to note is the “Scan Stacks Folder” option in the drop-down menu. I haven’t really needed to use it as Dockge tends to find my compose files on its own, but it’s worth mentioning.