Maintenance of Conda environment, Gemfile and Gemfile.lock #1127
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
|
This means we need a compiler and other stuff to get a website running, is that a correct understanding? |
Yes, although this is the case without the changes from this PR as well. The local build was not working without calling bundle and one of the ruby gems wants a compiler. The compiler is not in this PR because it was merged in #1123. |
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.
The logic behind using the Gemfile and Gemfile.lock for Ruby gems instead of a mixture of them with Conda is of course being able to take advantage of the Dependabot fix. As a side effect hopefully the whole setup is less chaotic.