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

DataScienceTutorials.jl deployment #1080

Open
ablaom opened this issue Feb 26, 2024 · 1 comment
Open

DataScienceTutorials.jl deployment #1080

ablaom opened this issue Feb 26, 2024 · 1 comment

Comments

@ablaom
Copy link

ablaom commented Feb 26, 2024

We are carrying out maintenance of DataScienceTutorials.jl which was built on Franklin (by @tlienart) and have the following problem.

It is a while since individual tutorials were updated. Before working on those updates, we wanted to make some orthogonal structural changes in how the landing page looks, and so forth. However, when we trial deployment, it looks like Franklin is generating its own tutorial Manifest.toml files (with latest, and so incompatible, versions of packages) instead of the "static" ones that accompany each tutorial. Is there any way to force Franklin to use the provided Manifest.toml's instead of generating the latest? In other words, can we make new deployments without having to update the tutorials every time?

cc @EssamWisam

@ablaom
Copy link
Author

ablaom commented Feb 26, 2024

In particular, is there any reason why we can't replace the Pkg.update() commands in lines like this one with Pkg.instantiate() ?

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