-
Notifications
You must be signed in to change notification settings - Fork 113
Add codespace config for scipy 2023 #184
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
Conversation
737ee9d
to
98e59b7
Compare
for more information, see https://pre-commit.ci
4a0606b
to
a1ca440
Compare
for more information, see https://pre-commit.ci
} | ||
} | ||
] | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will now open up another terminal and run jupyter lab
as soon as the codespaces open, so user would only need to cmd + click
the link.
for more information, see https://pre-commit.ci
@dcherian Once this is merged, someone with admin access to the repo should make a codespaces pre-build to speed up launching process: https://docs.github.com/en/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds |
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
This is really neat @lsetiawan thanks for trying it out. I followed the instructions using the badge pointing to your fork, and am able to launch jupytlab but not execute 01_datastructures.ipynb. I'm seeing a lot of 403 messages in the vscode terminal: |
Okay. Let me check it out... I haven't really tried the Jupyterlab instance when it's launched automatically, I used the manual launching and it worked. 😛 |
for more information, see https://pre-commit.ci
@lsetiawan (and everyone on the xarray-tutorial team) you should have Admin privileges on this repo :) Use wisely! |
This would definitely be helpful b/c installing the conda environment takes a while. An alternative approach (that I think is effectively the same but with a little more transparency) would be to build a Docker image via github actions and store at |
I wonder which storage is cheaper at that point since that would be more of a dev time cost. |
Co-authored-by: Scott Henderson <scottyhq@gmail.com>
I thought public repository packages on ghcr.io are free? In any case happy with the current setup which I tested (on Safari) and am successfully running the notebooks, and we can revisit in follow-up PRs |
Idk, haven't really used that one ;) If so, then it's better to use that! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed it's working well for me (tested on both safari and chrome). Thanks @lsetiawan this is great!
* upstream/main: move custom accessors to advanced and add more complex, runnable examples (xarray-contrib#168) Update and reorganize apply_ufunc material (xarray-contrib#180) Add jupyterlab-myst 2.0 and sphinx-exercise (xarray-contrib#187) Add jupyterlab-myst (xarray-contrib#182) Add codespace config for scipy 2023 (xarray-contrib#184) Add SciPy Instructions (xarray-contrib#183) Edits to "Xarray and Dask" (xarray-contrib#177) Setup PR Preview workflow (xarray-contrib#175) contents write permissions for github token (xarray-contrib#178)
Overview
This PR adds codespaces option for the repository based on the pangeo based image and the conda lock file. It will also copy the jupyter config file, as well as a vscode tasks json, so running clicking the url from terminal is the only thing a user would have to do.