Allow configuration via environment variables #449

Closed
opened 2022-12-14 07:53:46 +00:00 by pinpox · 2 comments

Especially for secrets, it would be very handy to allow configuration via environment variables instead of having them written in plaintext in the configuration file.

This would make deployment via Nix and other deployment tools easier.

Possible implementations would be to read variables like RPC_SECRET directly, or allow specifying them as $VARIABLE in the toml config.

Alternatively, allow specifying the secrets in separate files, so that these can be provided separately form the main configuration with something like rpc_secret_file instead of rpc_secret

Especially for secrets, it would be very handy to allow configuration via environment variables instead of having them written in plaintext in the configuration file. This would make deployment via Nix and other deployment tools easier. Possible implementations would be to read variables like `RPC_SECRET` directly, or allow specifying them as `$VARIABLE` in the toml config. Alternatively, allow specifying the secrets in separate files, so that these can be provided separately form the main configuration with something like `rpc_secret_file` instead of `rpc_secret`
lx added the
action
for-newcomers
kind
improvement
labels 2022-12-14 09:50:43 +00:00
Contributor

The last paragraph of this was handled in #466.

The last paragraph of this was handled in #466.

Could be nice to also have the admin token be configured by a file, or at least support env vars for just the "sensitive" variables.

It would mean you could check in your config file to git without exposing secrets and could make docker-compose nicer

Could be nice to also have the admin token be configured by a file, or at least support env vars for just the "sensitive" variables. It would mean you could check in your config file to git without exposing secrets and could make docker-compose nicer
lx closed this issue 2023-02-06 14:18:59 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#449
No description provided.