Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document configuration precedence and behaviour #97

Open
drewsonne opened this issue Apr 22, 2018 · 0 comments
Open

Document configuration precedence and behaviour #97

drewsonne opened this issue Apr 22, 2018 · 0 comments

Comments

@drewsonne
Copy link
Contributor

drewsonne commented Apr 22, 2018

Expected Behavior

There should be more details regarding the explicit behaviour of the precedence between config file, CLI options, and environment variables.

Current Behavior

There is a description of what the config options do, but not which sources have precedence.

Possible Solution

Write a section in the readme describing this.

Context (Environment)

When trying to deploy this en masse, I noticed that the seconds_duration option was being overridden.
During development, there was inconsistency in the approach taken to handling configuration and some documentation would crystalise this meaning

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant