Add lockfile installation helper function - #97
Open
flowln wants to merge 2 commits into
Open
Conversation
Signed-off-by: Sofia Donato Ferreira <sofia.ferreira@lnls.br>
flowln
added
enhancement
flowln
force-pushed
the
feat/remote-lockfile
branch
3 times, most recently
from
July 7, 2026 18:34
633403f to
4d42d6c
Compare
This should allow us to use lockfiles to install package dependencies instead of manually specifying them to install_packages. Signed-off-by: Sofia Donato Ferreira <sofia.ferreira@lnls.br>
flowln
force-pushed
the
feat/remote-lockfile
branch
from
July 8, 2026 13:22
4d42d6c to
10ca688
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is an experiment to improve reliability of production environments in beamlines. The idea is to generate controlled lockfiles for production use (e.g. via CI/CD), which then forces the environment to remain immutable until the next update. This should ensure that we don't get surprises in inconvenient timings, like outside work hours.
The HTTP support is intended to provide us the possibility of consulting CI artifacts from GitLab, maintaining an easy CD pipeline for the developer.