Global .env file

[trythatagain]

Just started to look at this project, very nice!
But 1 feature is missing for me, I use OMV and it has a feature I really, really like, that is a global .env file. I keep things like

• Time Zone
• PGID & PUID
• Various Dir locations
• etc.

I know I can use a local .env, but I'd have to copy and paste each container, which is a pain.
Also using a global .env you only have to edit 1 file for variables you use a lot.

I don't program, but I think the local .env file would overwrite the global .env file when doing a 'docker compose up', perhaps a toggle could be used in the setting menu, where if a global .env file is setup then you'd only then have to add the global .env file to the 'up' command, but I don't think anything bad happens even if you add a blank .env fle to the 'up' command.

What does anyone else think?

[lephtHanded]

I use Dokemon specifically for this purpose.

[trythatagain]

Just had a look, it's not been touched in 3 years.
Plus I like the graphics etc in Dockhand, I have written a script that will copy and cat to a .env for OMV, but still would prefer a global .env, OMV compose plugin works well, but does mean logging into server to use it though. Did look at Dockage, but TBH Dockhand is probably the best looking for me as a simple home labber.

[Zaf9670]

Just wanted to +1 this idea.

[Delver26]

I'm also an OMV user and it's an extremely helpful feature. Being able to define a variable a single time and then can be referenced across all stacks is a big QOL improvement.
+1 for this suggestion.

[ido-nl]

I was wondering about this as well. I can create config sets, but they only apply for containers, not stacks.
All my containers use a set of the same configuration, there GUID, UUID and TZ are the most basic ones.

So for me also a +1 for this idea.

[radoeka]

May the new Context Directory implement what you're looking for?

[ido-nl]

Maybe, trying to figure out how this works, think only when getting the compose file from GIT.

[trythatagain]

I agree this looks like a feature that can only be used via GIT. As I don't use GIT in my homelab, it's not really what I want.

I want a global .env file that can be used by all compose files. You define the global .env file once, and it's either applied by default, or perhaps a checkbox for each stack. It's such a useful feature and makes life so much easier when using the same variables in most of your stacks.

[jlmanohar]

On a side note :
I tired mounting a docker mount with a .env file on container's /env/.env/
and then in the stacks page referenced it with the absolute path, but it doesn't seem to work, is the additional env file always relative to context directory ? or absolute paths allowed ?