-
Notifications
You must be signed in to change notification settings - Fork 0
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
Use conda-lock #165
Use conda-lock #165
Conversation
Fixes #164
Using mamba failed due to pinned python=3.10
…mdspawner with pip
Aka the generated notebook uses v1 pyewatercycle
2 conda-lock files (one from ewatercycle repo and one for jupyter) can not be be merged. So we first install the conda-lock from ewatercycle repo and then use a conda env file with pinned versions to install jupyter. |
To do second vagrant provision I had to fix vagrant see |
roles/ewatercycle/templates/environment.yml.j2 now has direct dependencies pinned. This should be more reproducible, but you will miss security updates and deps of deps can still break things. |
I guess the alternative would be to built a completely new conda-lock file from scratch? Is that possible/viable/desirable? |
==REVERSE_PROXY== does not work like that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Things work now 👍
Fixes #164
Also
To test