We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I wonder if we should split our file
alrecon/settings/***'yaml
in e.g. 3 files, one for file paths that might regularly change, one for general settings, and for the HPC configuration.
The text was updated successfully, but these errors were encountered:
What I additionally get is that the format (keys) of the first read settings file determines the keys of all following files,
Breaking changes and error search could be mitigated and facilitated, also because different writing and reading steps could be performed.
Sorry, something went wrong.
gianthk
phlpphns
No branches or pull requests
I wonder if we should split our file
alrecon/settings/***'yaml
in e.g. 3 files, one for file paths that might regularly change, one for general settings, and for the HPC configuration.
The text was updated successfully, but these errors were encountered: