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

Roadmap #34

Open
4 of 8 tasks
krischer opened this issue Oct 4, 2019 · 4 comments
Open
4 of 8 tasks

Roadmap #34

krischer opened this issue Oct 4, 2019 · 4 comments
Assignees

Comments

@krischer
Copy link
Collaborator

krischer commented Oct 4, 2019

  • Finish Convert everything to Jupytext #33 (@sebnoe @krischer)
  • Docker base image (@megies)
    • pre-built custom Docker image on binder works well
    • big data files can be included in pre-built Docker image by modifying docker_baseimage/Dockerfile.seismo-live-base and building a new base image (hosted on docker hub)
    • Python environment will be stable and stay at consistent module version numbers, ensuring the notebooks keep working, after being verified once
    • currently notebooks inside the started binder can be updated manually by starting a Terminal in the jupyter notebook and doing e.g. git pull. No automatic update to current master right now
  • Auto-generate index page (@krischer)
  • Public relations and 💵 (@heinerigel)
  • Add new notebooks (@heinerigel)
  • Find a nice solution for the animations (@sebnoe)
@megies
Copy link
Member

megies commented Oct 21, 2019

@sebnoe i can not ever get mybinder to start, actually. Not on master and not on binder_dockerfile. Last time you said it works for you just taking long sometimes, what exactly were you doing to get it started?

@megies
Copy link
Member

megies commented Oct 25, 2019

@heinerigel @krischer @sebnoe

Switching to a fully static install using pre-built docker images is ready now.

seismo-live can basically started in usually 40 secs to 2mins on mybinder.org:
https://mybinder.org/v2/gh/krischer/seismo_live/binder_dockerfile

I think #36 can be merged.

The way forward could be:

  • change the seismo-live website
    • move to a different host (since LRZ shuts down the current hosting next week)
    • auto-generate index page (links to notebooks will have to filled in dynamically with the URL response from mybinder.org, see below)
    • change how jupyter is embedded
      • when clicking "launch a new notebook" the website can start a binder via binderhub API on mybinder.org in the background
      • individual notebooks in the directory tree can directly link to the notebooks by inspecting the ready HTTP response, e.g. linking to https://hub.gke.mybinder.org/user/krischer-seismo_live-yhz2uk7m/notebooks/seismo_live/notebooks/Ambient%20Seismic%20Noise/Probabilistic%20Power%20Spectral%20Densities.ipynb

Other changes can come after this step, I think..

  • jupytext setup
  • notebook testing in CI
  • fix animations and individual notebooks

@megies
Copy link
Member

megies commented Oct 25, 2019

The only point which is still a bit unclear is whether we need to and/or how to best update notebooks when the pre-built docker image is started. But this is a secondary issue, for now we can just build a new docker base image if we want the notebooks updated. See https://github.com/krischer/seismo_live/tree/binder_dockerfile/docker_baseimage#final-setup-steps-in-docker

@megies
Copy link
Member

megies commented Oct 29, 2019

@krischer is there an easy option to have an interim website for seismo-live.org hosted at LRZ that will just provide a link to https://mybinder.org/v2/gh/krischer/seismo_live/binder_dockerfile instead of the current tmpnbserver getting started in LRZ cloud?

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

4 participants