Skip to content
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

Provide requirements-freeze files as backup #223

Closed
rmarquis opened this issue Oct 1, 2024 · 1 comment
Closed

Provide requirements-freeze files as backup #223

rmarquis opened this issue Oct 1, 2024 · 1 comment
Assignees

Comments

@rmarquis
Copy link
Contributor

rmarquis commented Oct 1, 2024

While we teach how and why generating a requirements-freeze.txt file in the guide, we do not procide such files to the readers. Indeed, the objective is to teach how to do it as a best practive.

This also means that we don't have full control of transitive dependency in the guide, and breakage might occur (the latest time in #221). In practice, this means the guide might stop working between the time we last test the content, and the time the content is read.

To avoid annoying some awkward in teaching environement, we can provide pre-generated requirements-freeze.txt files, as backup in case a breakage arise.

Prepare backup requirements-freeze.txt files for each chapter, and upload them in a separate freeze-backup branch.

If needed, the content could be accessed manually or with wget:

# Download the requirement-freeze.txt backup
wget https://github.com/swiss-ai-center/a-guide-to-mlops/freeze-backup/refs/heads/requirements-freeze-chapterX.txt -O requirements-freeze.txt

Ensure this branch is correctly updated when needed.

@rmarquis rmarquis self-assigned this Oct 1, 2024
@rmarquis
Copy link
Contributor Author

rmarquis commented Oct 1, 2024

Done, in the freeze branch.

@rmarquis rmarquis closed this as completed Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant