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 only settings file, not envars #11

Open
supremebeing7 opened this issue Jun 10, 2016 · 0 comments
Open

Use only settings file, not envars #11

supremebeing7 opened this issue Jun 10, 2016 · 0 comments

Comments

@supremebeing7
Copy link
Owner

There's a weird mix of using envars and settings.yml file for user inputs, where it saves the input to an envar, then writes it to the settings file. When reading, it fetches the yml file values and writes them to envars. All of the classes use envars instead of pulling directly from the settings file.

Essentially, there's no point in using envars when we could easily just use the settings file, and read from/write to it directly. Probably by defining a Settings class for easier fetching/writing.

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

No branches or pull requests

1 participant