Setting up Tercen Studio

If you wish to develop operators then you need to set up a development environment.

Installing Tercen Studio

1. Install docker-compose

First you need to install docker-compose.

For Windows:

If you use Windows, you can install Docker-Desktop for Windows that includes docker-compose.

Advise: Select the WSL 2 backend system option when installing on Windows.

For Mac and Linux:

Check out how to install docker-compose on Mac or Linux.

2. Clone tercen-studio repository

Then, get tercen-studio by cloning the following repository:

git clone https://github.com/tercen/tercen_studio.git
cd tercen_studio

The latest instructions on how to install Tercen Studio can be found in the README of the Tercen Studio GitHub repository.

Starting Tercen Studio

Once docker-compose is installed and the tercen-studio repository cloned, you can start tercen by running:

# optional but recommended: lets the studio install operators from private
# GitHub repositories and pull private ghcr.io images. Use a CLASSIC personal
# access token with `repo` scope (fine-grained github_pat_… tokens are not
# accepted by the git zipball endpoint).
export GITHUB_TOKEN=ghp_your_token_here

docker compose up -d

Since 2026-08 the studio runs the same released images and architecture as production: tercen main + a separate worker (each running podman internally — the main manages the sarno table engine, the worker executes operator containers), ha-scheduler, redis and couchdb. The bundled RStudio ships R 4.4.3 — the same version as the runtime-r44 operator base image, so results computed in RStudio are trustworthy against CI. Image versions are pinned in docker-compose.yaml; to update, bump them to the currently deployed production versions. Upgrading from a pre-2026-08 studio: the architecture changed — run docker compose down -v (wipes local data) and start fresh. For GPU operator development see the GPU chapter — and use tercen/gpu_smoke_operator to verify GPU passthrough on any Tercen instance.

You can run Tercen by going to http://127.0.0.1:5402.

Username: admin
Password: admin

You can run RStudio by going to http://127.0.0.1:8787/.

Username: rstudio
Password: tercen

VS Code (Python development) is optional; start it with docker compose --profile python up -d and open http://127.0.0.1:8443/.

Password: tercen

Now you’re all set!

# Setting up Tercen Studio {-} If you wish to develop __operators__ then you need to set up a development environment. ## Installing Tercen Studio {-} **1. Install docker-compose** First you need to install [docker-compose](https://docs.docker.com/compose/install/). **For Windows:** If you use Windows, you can install [Docker-Desktop for Windows](https://docs.docker.com/docker-for-windows/install/) that includes `docker-compose`. **Advise**: Select the __WSL 2 backend__ system option when installing on Windows. **For Mac and Linux:** Check out [how to install docker-compose](https://docs.docker.com/compose/install/) on Mac or Linux. **2. Clone tercen-studio repository** Then, __get tercen-studio__ by cloning the following repository: ```bash git clone https://github.com/tercen/tercen_studio.git cd tercen_studio ``` The latest instructions on how to install Tercen Studio can be found in the README of the [Tercen Studio GitHub repository](https://github.com/tercen/tercen_studio). ## Starting Tercen Studio {-} Once `docker-compose` is installed and the `tercen-studio` repository cloned, you can __start tercen__ by running: ```bash # optional but recommended: lets the studio install operators from private # GitHub repositories and pull private ghcr.io images. Use a CLASSIC personal # access token with `repo` scope (fine-grained github_pat_… tokens are not # accepted by the git zipball endpoint). export GITHUB_TOKEN=ghp_your_token_here docker compose up -d ``` Since 2026-08 the studio runs the same released images and architecture as production: `tercen` main + a separate worker (each running podman internally — the main manages the `sarno` table engine, the worker executes operator containers), `ha-scheduler`, `redis` and `couchdb`. The bundled RStudio ships **R 4.4.3 — the same version as the `runtime-r44` operator base image**, so results computed in RStudio are trustworthy against CI. Image versions are pinned in `docker-compose.yaml`; to update, bump them to the currently deployed production versions. **Upgrading from a pre-2026-08 studio:** the architecture changed — run `docker compose down -v` (wipes local data) and start fresh. For GPU operator development see the GPU chapter — and use [`tercen/gpu_smoke_operator`](https://github.com/tercen/gpu_smoke_operator) to verify GPU passthrough on any Tercen instance. You can run **Tercen** by going to [http://127.0.0.1:5402](http://127.0.0.1:5402). * _Username_: admin * _Password_: admin You can run **RStudio** by going to [http://127.0.0.1:8787/](http://127.0.0.1:8787/). * _Username_: rstudio * _Password_: tercen VS Code (Python development) is optional; start it with `docker compose --profile python up -d` and open [http://127.0.0.1:8443/](http://127.0.0.1:8443/). * _Password_: tercen Now you're all set!