Update instructions for containerization #200
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HealthyPear
added
documentation
Codecov Report
@@ Coverage Diff @@
## master #200 +/- ##
=======================================
Coverage 63.11% 63.11%
=======================================
Files 28 28
Lines 2890 2890
=======================================
Hits 1824 1824
Misses 1066 1066 Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instructions have been updated after successful testing of the deployment of both development and released version Docker containers from the big interface upgrade (v0.4.0).
Singularity containers are not maintained anymore and should be avoided (though the recipe should still work so I left those instructions).
The Docker images are stored under my personal account.
As soon as we merge everything under cta-observatory we can create a user for that.
Even better - we migrate (after the merge) to GitLab and use the Container Registry there.