You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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
The text was updated successfully, but these errors were encountered: