Split yaml from appdata #516
-
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
I too use OMV7, but tend to use the compose plugin, until Dockge has a global .env built in (I know there is a workaround, but I want it built in) . I then just use something like the following in my compose files, I just checked OMV and the 'appdata' shared folder in settings is optional, so I don't actually use it, I just place my appdata folder as a volume in all my compose files. Which means you can have more than 1 appdata folder.
|
Beta Was this translation helpful? Give feedback.
-
Right I think I can see whats wrong, I'll try and explain it as best as I can, if I don't come across right just please ask. OMV and Dockge have different compose file names - OMV 'container.yml' and 'container.env' + the 'global.env', Dockge 'compose.yml' and '.env' (I did ask compose plugin maintainer if he's change to default name, and he declined, which is fair enough) So because we set the below volume, Dockge can see containers that are up.
In my setup Dockge will say they are active, but thats it, I can't 'down' it, and thats because of the compose file names. I did write a simple script that will go thru the 'compose' folder and copy 'container.yml' to 'compose.yml' then take 'global.env' and 'container.env' file and copy it to '.env' file. This then allows me to mess about with Dockge, I think I might have either posted it or asked if anyone wanted me to, and no-one replied so I lost interest :( Just remember everything in OMV uses a database, so all the compose files that OMV saved have to be edited from within OMV for changes to stick. So if you changed the 'compose.yml' or '.env' with Dockge and still want it to show in OMV you'll need to edit in OMV or I change in OMV and then run my script. But when Dockge has global .env, I might ditch the compose plugin as it does loads I don't even look at. |
Beta Was this translation helpful? Give feedback.
-
Thats homelabing for you, always something else shiny and new around the corner :) |
Beta Was this translation helpful? Give feedback.
Right I think I can see whats wrong, I'll try and explain it as best as I can, if I don't come across right just please ask.
OMV and Dockge have different compose file names - OMV 'container.yml' and 'container.env' + the 'global.env', Dockge 'compose.yml' and '.env' (I did ask compose plugin maintainer if he's change to default name, and he declined, which is fair enough)
So because we set the below volume, Dockge can see containers that are up.
In my setup Dockge will say they are active, but thats it, I can't 'down' it, and thats because of the compose file names.
I did write a simple script that will go thru the 'compose'…