Environment Variables #29161
|
Hi, Firstly, big thanks to the Immich team and all the contributors ❤️ I was looking through the documentation for the environment variables and saw: 
But in a freshly downloaded example docker compose, it still has these messages: 
Since these env vars aren't used by the containers directly, just the compose file, is there actually any reason I can't hardcode the paths? The specific environment variables I'd like to hardcode directly are UPLOAD_LOCATION and DB_DATA_LOCATION. All my other containers are perfectly fine with hardcoded paths in the compose, so I was just wondering if there's a technical reason these couldn't be the same, or if it's just personal preference from the maintainers? Thank You |
Replies: 2 comments 1 reply
|
For extra context, I have a bunch of scripts to manage my whole selfhosting stack - I wouldn't be editing this compose directly, so it's not an issue that I might update the wrong path (container instead of the host) |
|
You can do whatever you want. Use env, not use it. Up to you. This is just a generic preset given as an example. There are reasons to split a compose and env but if you don't want too, doesn't really matter. |
|
Thank you for the confirmation. |
You can do whatever you want. Use env, not use it. Up to you. This is just a generic preset given as an example. There are reasons to split a compose and env but if you don't want too, doesn't really matter.