For the complete documentation index, see llms.txt. This page is also available as Markdown.

Working in Your Instance

Every managed compute instance runs three editors—JupyterLab, code-server, and R Server—against the same files. Use whichever you prefer, or switch between them mid-project.

Connect from the GoFigr web app: when an instance is Running, click the Jupyter, code-server, or R Server button to open that editor in a new tab. (Connect links are tied to you as the owner.)

Where your files live

Your home directory is /home/gofigr/notebooks. It's seeded on first boot with:

  • START-HERE.md — a short welcome and orientation.

  • examples/ — a runnable example notebook (tcga_lung_classifier.ipynb) and its Quarto/R counterpart (tcga_lung_analysis.qmd).

Everything in your home directory lives on the instance's data volume and persists across stop/start.

The editors

The GoFigr IPython extension is pre-installed. In a notebook, capture starts as soon as you load it:

%load_ext gofigr

From there, figures you create are published automatically—no credentials to set up, because the instance is already signed in to your account. See the Python integration for what's captured and how.

The Python environment

Python runs from a virtual environment at /home/gofigr/venv. It lives on your data volume, so anything you install persists across restarts, and it's already active in JupyterLab and the code-server terminal—you don't need to activate it. The gofigr client is installed here, and pip install and the notebook kernel both resolve to this environment.

If you open a plain login shell and want it active explicitly:

Installing extra packages

The instance comes pre-loaded with common Python and R packages. Need more? Add them from the integrated terminal or a notebook cell—they install to your data volume and persist across restarts:

Because installed packages live on your persistent data volume, you only install each one once—it'll be there the next time you start the instance.

Last updated