Dockge to Dockhand #84
Replies: 4 comments 4 replies
-
|
Edit: Somebody has already tried it: #8 (comment) @angeloschat, I kinda doubt it will. My guess is that the Dockhand stacks internal records are stored in the database, with the files that comprise the stacks stored in /app/data/stacks. It might not hurt to try. No need to point to your genuine compose files, though. Drop a copy of the Dockge compose files into the Dockhand /app/data/stacks folder. My guess is that Dockand will just ignore them and continue to show them as External. Import is on the roadmap, though.
|
Beta Was this translation helpful? Give feedback.
-
|
Adopt feature is almost ready, if you want to test a dev build
|
Beta Was this translation helpful? Give feedback.
-
|
Excellent! This is very nice feature. |
Beta Was this translation helpful? Give feedback.
-
|
Hi. Mount your actual docker-compose volume to: The adopt them all from /compose Only thing at this point I think was not able to fix is to make this the default location when you create a new docker-compose container. I need to switch folder manually. |
Beta Was this translation helpful? Give feedback.




Uh oh!
There was an error while loading. Please reload this page.
-
I want to move to Dockhand from Dockge.
Dockge keeps the compose files (stacks in Dockhand) under /opt/stacks/name/ with compose.yaml file and optionally .env file
The default Dockhand volume is - dockhand_data:/app/data.
If I mount the /opt/stacks:/app/data will Dockhand "take over" the stacks from Dockge and show them as internal?
That would be great.
Beta Was this translation helpful? Give feedback.
All reactions