# Running Code Studios[¶](https://doc.dataiku.com/dss/latest/code-studios/running.html#running-code-studios "Permalink to this headline")

Code Studios are created from template in projects.

* Sample: Running JupyterLab

* Project exports and bundles

## Sample: Running JupyterLab[¶](https://doc.dataiku.com/dss/latest/code-studios/running.html#sample-running-jupyterlab "Permalink to this headline")

After having built the template as described in Preparing Code Studio templates:

* ensure the project is associated to a cluster, either by setting a default cluster in “Administration > Settings > Containerized execution” or by setting a cluster for the project in its “Settings > Cluster selection”

* in the “Code Studios” section, click **New Code Studio**, select the `jupyter-lab-template` template, fill a name and create the Code Studio

* once in the Code Studio, click **Start**

After the Code Studio has started, you get access to a Jupyterlab server instance. Work done in the Code Studio will usually materialize as modified files in the container. These would disappear when the Code Studio is stopped, so in order to safekeep them, synchronizing them back to the DSS server’s filesystem is needed, with the **Sync files with DSS** button.

## Project exports and bundles[¶](https://doc.dataiku.com/dss/latest/code-studios/running.html#project-exports-and-bundles "Permalink to this headline")

When exporting or bundling a project, only Code Studios that are published as webapps are included. For included Code Studios, both versioned and resource files of the Code Studio are exported. But project resources are not exported by default, and need to be manually checked, if some of the published Code Studios use them.

Note

Code studio templates are not included in bundles, and need to be installed separately on the target node, with the same name. As with plugins, the user gets a warning with the list of templates installed on the node from which the bundle originates.
