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

Use YAML instead of env. vars. for HW configuration. #37

Open
arnoldandreasson opened this issue Apr 29, 2021 · 1 comment
Open

Use YAML instead of env. vars. for HW configuration. #37

arnoldandreasson opened this issue Apr 29, 2021 · 1 comment

Comments

@arnoldandreasson
Copy link
Member

Future development will need more configurable parts. YAML is better suited for that and integrates well with Python.
If the default YAML-file is stored as a Git controlled file and the detector check for a YAML-file in /home/pi/wurb_settings before the default location then there will be no problems with the git pull command.

@slowglow
Copy link

I strongly agree with the need to move the configuration settings from environment variables to something else. I will certainly use them in the future.

Not wishing to start a flame war here, because as am not knowlegeable enough and have no preference about either of them, but have you considered TOML vs YAML? I am only asking, because I recently tried to use poetry for python project management and it uses TOML file, which was advertised as much better than 'requrements.txt` and anything else before :-).

Putting the visual difference aside, what would be the top three technical arguments to choose one over the other (YAML vs. TOML)?

I know that sometimes these discussions can get bogged down in a typical example of bike-shedding and I accept that developers personal experience and preference is valid reason to select one over the other. Still, it could be useful to have a quick evidence-driven comparison.

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

2 participants