Skip to content
This repository has been archived by the owner on Apr 5, 2024. It is now read-only.

Configuration File #51

Open
0xcaff opened this issue Aug 16, 2018 · 2 comments
Open

Configuration File #51

0xcaff opened this issue Aug 16, 2018 · 2 comments

Comments

@0xcaff
Copy link
Member

0xcaff commented Aug 16, 2018

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:

  • ffmpeg path
  • serve bind host

fixture_setup

Currently, dotenv is used for some configuration in fixture setup.

Solutions

  • config-rs
  • environment variables
@0xcaff 0xcaff mentioned this issue Aug 18, 2018
14 tasks
@AzureMarker
Copy link
Member

toml is easy to use for configs.

@0xcaff
Copy link
Member Author

0xcaff commented Sep 19, 2018

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants