Is your feature request related to a problem? Please describe.
I don't want to have secrets (eg pfsense api key, postgres pw) in the config file
Describe the solution you'd like
Accept env vars with file paths from which to read the secrets (e.g. WGPORTAL_PFSENSE_APIKEY_FILE)
Describe alternatives you've considered
You could also add env vars without the _FILE so users can specify in a .env file (not much more secure than having in the config file, but still lets you decouple secrets)
Additional context
This pattern is used by many community containers (authelia, postgres) to facilitate use of docker secrets
Is your feature request related to a problem? Please describe.
I don't want to have secrets (eg pfsense api key, postgres pw) in the config file
Describe the solution you'd like
Accept env vars with file paths from which to read the secrets (e.g.
WGPORTAL_PFSENSE_APIKEY_FILE)Describe alternatives you've considered
You could also add env vars without the
_FILEso users can specify in a .env file (not much more secure than having in the config file, but still lets you decouple secrets)Additional context
This pattern is used by many community containers (authelia, postgres) to facilitate use of docker secrets