FAQ - RWTHjupyter
- Yes. Please issue the role "Angehörige Organisationseinheit" to the external partners, so that they can access the university's IT services.
- You can then share your Jupyter Notebooks with your external partners.
- Partners can access RWTHjupyter but might have reduced privileges and/or priorities.
last changed on 03/26/2026
(opens in new tab)This work is licensed under a Creative Commons Attribution - Share Alike 3.0 Germany License (opens in new tab)
- We use a Jupyter extension called nbgitpuller (opens in new tab) to sync Jupyter Notebooks. nbgitpuller uses an "automatic merging behaviour" to sync changes between your local home directory and the upstream Git repo. Please consult the nbgitpuller documentation for details about this merging behaviour (opens in new tab).
last changed on 06/04/2025
(opens in new tab)This work is licensed under a Creative Commons Attribution - Share Alike 3.0 Germany License (opens in new tab)
- Currently, GPUs are only available for selected courses. Please contact us if you wish to use GPU resources.
last changed on 04/09/2026
(opens in new tab)This work is licensed under a Creative Commons Attribution - Share Alike 3.0 Germany License (opens in new tab)
As part of the transition from git.rwth-aachen.de to the new GitLab instance at gitlab.git.nrw (opens in new tab), the repositories used by RWTHjupyter (notebook repository and container image repository) must be migrated.
This migration is required for git.rwth-aachen.de by July 1, 2027, at the latest. A migration from git-ce.rwth-aachen.de is also planned, but the date has not yet been set. You can find the latest information on this on the General Information about GitLab page.
To ensure we can properly integrate the new repositories into RWTHjupyter, please submit a ServiceDesk ticket (Send an email to:) via email with the information listed below. The request must be submitted by one of the designated contacts for the respective repository:
- Full URL of your Notebook Repository (contains your Jupyter notebooks)
- Full URL of your container image repository (contains the Docker images for RWTHjupyter)
- Deploy tokens or deploy keys (if available)
- If the project is public, no deploy tokens or deploy keys are required
- The profile slug/abbreviation associated with the repositories
last changed on 08/10/2026
(opens in new tab)This work is licensed under a Creative Commons Attribution - Share Alike 3.0 Germany License (opens in new tab)
The existing GitLab instance git.rwth-aachen.de will be replaced by gitlab.git.nrw. To ensure that RWTHjupyter can continue to access your data, the repositories must be migrated.
You cand find instructions on how to migrate your repositories in our FAQ: How do I migrate RWTHjupyter repositories to the new GitLab instance?
last changed on 08/10/2026
(opens in new tab)This work is licensed under a Creative Commons Attribution - Share Alike 3.0 Germany License (opens in new tab)
Yes, both the notebook repository and the container image repository must be migrated for RWTHjupyter to work properly.
last changed on 08/10/2026
(opens in new tab)This work is licensed under a Creative Commons Attribution - Share Alike 3.0 Germany License (opens in new tab)
If you do not migrate your repositories, the following will happen:
- RWTHjupyter will no longer be able to access your data as of July 1, 2027.
- Your notebooks will no longer be available for students to load after that date.
- Your container images will still be available, but they can no longer be updated.
last changed on 08/10/2026
(opens in new tab)This work is licensed under a Creative Commons Attribution - Share Alike 3.0 Germany License (opens in new tab)
