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

Possible switch of Pluto notebook environment and using dev version of EpiAware #398

Closed
SamuelBrand1 opened this issue Jul 25, 2024 · 1 comment

Comments

@SamuelBrand1
Copy link
Collaborator

          Replying to a comment above:

i.e do we really need to support this workflow?

I haven't done this... but an option is to stop using a development approach to EpiAware for the pluto based showcases and just install EpiAware from main. Additionally, if we want we can pin the dep versions using Pkg rather than relying on finding a local path to the docs env.

The main downside is that a change to EpiAware in a branch will no longer be represented in the output of the pluto notebook. The main upside would be that each pluto nb we use will be portable; you could download it by itself and it will run locally for you from the Pluto interface without needing to install EpiAware or any of the deps.

Originally posted by @SamuelBrand1 in #395 (comment)

@SamuelBrand1
Copy link
Collaborator Author

This just replicates #396 !

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