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.

Sign up for GitHub

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

Jump to bottom

Investigate change in how config is populated #472

Open

johnhbenetech opened this issue Mar 3, 2022 · 0 comments

Member

johnhbenetech commented Mar 3, 2022

Previously, a user would change default.config.yaml in the root directory which would be converted to config/config.yaml during initial run.

Now: config/config.yaml exists before first run so the user has to know to change config there.

Is this change intended? if so, what's the purpose of default.config.yaml

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