Codespaces¶
A codespace, similar to a repository or folder file tree structure, can contain any number of files and nested folders. Notebooks included in a codespace are represented as a persistent file (.ipynb), just like any of the other non-notebook files within a codespace. While a DataRobot Notebook is treated as a single top-level asset, a codespace can contain any number of notebooks. In addition to the persistent file storage, the codespace interface includes a file editor and integrated terminal for an advanced code development experience. Within a codespace you can:
- Open, view, and edit multiple notebook and non-notebook files at the same time.
- Execute multiple notebooks in the same container session (with each notebook running on its own kernel).
- Version notebook files as well as non-notebook files in external Git repositories using the Git CLI.
DataRobot supports cloud versions of GitHub, GitLab, Bitbucket and Microsoft Azure Repos. It also supports GitLab Enterprise Self-Managed for on-premise and STS deployments.
| Topic | Description |
|---|---|
| Add a space and start a session | How to create, run, and manage a a DataRobot codespace session. |
| Use Git with codespaces | How to use an external Git repository. |
| Connect a local IDE to a codespace | How to open a codespace from Visual Studio Code over SSH. |
| Notebook scheduling | The configuration options available for scheduling notebook runs. |
| Convert a notebook into a codespace | Learn about the options available for converting standalone notebooks into codespaces. |