-
Notifications
You must be signed in to change notification settings - Fork 2
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
Data init #205
Data init #205
Conversation
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Quirks with the way env_file includes files break some of the desired hierarchical loading of the Compose files. If .env.dev is loaded, in general the test results can be invalid.
In the process of fixing regressions caught by running the unit tests (Compose "ci" profile), I discovered more problems related the way Compose invludes files specified in the
Compose will still load the env vars in Passes the tests as of c5a527f. |
Fixes #203
Description of the Change
The data initialization routine has been refactored heavily, simplifying and further parameterizing locations of data files required by Blast. The integrity of all files is verified using md5sums, allowing the detection of the slightest change to a file or a missing file. The S3-compatible CLI client from MinIO,
mc
, was installed in the application image so thatmc mirror
can be used to pull data in a highly bandwidth and time efficient manner, downloading only the files that are invalid or missing. AFORCE_INITIALIZATION
env var was added as a convenience to clear the initialization lock files that can sometimes be left on the persistent data volume if initialization fails, typically during code development. A data source page was added to the acknowledgements section of the docs.