-
Notifications
You must be signed in to change notification settings - Fork 97
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
Add demo repositories mechanism to populate user's space #2207
Add demo repositories mechanism to populate user's space #2207
Conversation
Currently fixing an issue with permissions when executing the script, will commit the update in a few minutes once that's fixed |
…oud into vini-prepopulate-jlab
Fixed, now I will rename the yaml config field based on the suggestions given on the issue |
I've done some testing already, but now I will check with the examples we discussed during the last meeting |
Here are some tests by specifying the following in the jupyterlab:
initial_repositories:
- examples/nebari-demo: https://github.com/nebari-dev/nebari-demo.git
- examples/big-data: https://github.com/nebari-dev/big-data-tutorial-90min.git Screenshot from the initContainer running the clone:Image from the jupyterlab user pod:** Permission given to any git repository created by this method will always be When the pod is restarted, the script does not run again if the git repos already exists: |
Reference Issues or PRs
closes #2179
What does this implement/fix?
This PR exposes/introduces a new way to easily instantiate GitHub repositories in the user superlab pod during launch time. This helps streamline demos, examples, and other data that the administrator considers needed for any user who starts using the platform.
Description
The primary goal of this PR is to streamline the initialization and distribution of the Git repositories when a user first launches its JupyterLab instance. The main addition is simplifying the script's command-line arguments to make it easier to use within a Kubernetes context.
In the
nebari-config.yaml
side, a new field was included (optional) to distribute the location where the given repository will be cloned into (relative to the user/home
directory) and its URL.block syntax
Put a
x
in the boxes that applyTesting
Any other comments?