-
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
Implement dandi:files
extractor
#363
Implement dandi:files
extractor
#363
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #363 +/- ##
==========================================
+ Coverage 98.77% 98.81% +0.04%
==========================================
Files 55 55
Lines 2605 2626 +21
==========================================
+ Hits 2573 2595 +22
+ Misses 32 31 -1 ☔ View full report in Codecov by Sentry. |
This allows easy configuration to run multiple DL-Registry within the same host
On processed repos
@yarikoptic This PR is ready for merge. Upon your decision on whether to make the extracted metadata by datalad-registry/datalad_registry/conf.py Line 56 in b6e9d5b
|
…tors The extractor is not enabled for usual setups because of performance impact
@yarikoptic I think we should merge this one if you are OK with the implementation. If you are concerned with the performance impact, we can run the registry with the These is a live instance of DL-Registry with the changes in this PR and the |
This PR implements the
dandi:files
extractor. Additionally, it reorganizes the Docker compose files and dot env template files so that port of services at host can be changed easily. This ease of change of service ports at host facilitate running different instances of DL-Registry in the same host, allowing experimentation of different setup within a host.