If the total size of the files stored in your project’s Git repository exceeds 1GB, your project will experience slowdowns or become unresponsive. Anaconda advises maintaining an individual file size of less than 50MB each. If you need to work with files that exceed this threshold, speak with your cluster administrator.Furthermore, binary files are difficult for version control systems to manage, so Anaconda recommends using storage solutions designed for that type of data and connecting to those data sources from within your Workbench sessions.
If your organization would prefer to use its own supported external version control repository, your administrator can configure Workbench to use that repository instead of the internal GitHub server. For more information, see Connecting to an external version control repository.Once complete, you will be prompted for your personal access token before you create your first project in Workbench. For more information, see Configuring user access to external version control.
- Set your project’s name.
- Select a resource profile. This is a critical step for meeting computational demands of your project. For more information, see Understanding resource profiles.
- Choose a default editor for your project. The default selection is JupyterLab.
- Assign tags to your project. For more information, see Project tagging.
- Delete the project. For more information, see Deleting a project.`
editor
, sync
, and proxy
container, and logs for each container are accessible to aid in troubleshooting issues you may encounter with your project. For more information, see Project logs.

Working offline
To work on a project offline, download an archived version (tar.gz
) of the project from the projects page. When you are ready, you can upload the files you’ve modified back to the project in Workbench and commit your changes to make them available for other project collaborators. For more information, see Saving and committing changes in a project.