You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 5, 2024. It is now read-only.
There are variables which are used to configure the behavior of the program. They should be stored in a centralized location and documented. Here are some of the variables:
ffmpeg path
serve bind host
fixture_setup
Currently, dotenv is used for some configuration in fixture setup.
Solutions
config-rs
environment variables
The text was updated successfully, but these errors were encountered:
There are many different ways to configure an application. I'm against the idea of configuration files because they are state as a file. It is annoying to set settings of a docker container with configuration files. Environment variables are nicer for this. That said, environment variables give up structure. They don't allow for type checking (except at time used). Discoverability is worse.
I think because we have a few, using environment variables (potentially with dotenv) with sane defaults is the way to go.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem
There are variables which are used to configure the behavior of the program. They should be stored in a centralized location and documented. Here are some of the variables:
fixture_setup
Currently, dotenv is used for some configuration in fixture setup.
Solutions
The text was updated successfully, but these errors were encountered: