Testing & Runtime Environments¶
Central index of every supported way to run the course labs and documentation.
Use this page to choose an environment; follow the linked detailed guide for full setup steps.
As new options are added they will appear here first.
Current options at a glance¶
| Environment | Best for | Offline? | Live GCP? | Detailed guide |
|---|---|---|---|---|
| Docker + JupyterLab | Running all lab notebooks consistently | Yes | Optional (ADC) | docker.md |
| VS Code Dev Containers | Full IDE (editor, debugger, terminal, notebooks) inside the course image | Yes | Optional (ADC) | vscode.md |
| VS Code attach to Compose | JupyterLab already running + VS Code on the side | Yes | Optional | vscode.md |
| Google Colab | Zero local install, quick experiments | Partial | Optional | colab.md |
| Local MkDocs only | Previewing / editing the course site | Yes | N/A | See below |
| Live GCP (Terraform) | Real Cloud SQL, Vertex AI, GCS for the optional live lab paths | No | Yes | gcp-setup.md |
Environment details¶
Primary recommended path for the labs.
or
- Consistent Python 3.11 stack
- All lab notebooks and source mounted live
- Works fully offline; mount Application Default Credentials when you want live GCP
Full instructions → Docker / JupyterLab Environment
Open the repository root in VS Code and choose “Reopen in Container”.
Uses the same Docker image as the Jupyter stack so the environment stays identical.
Full instructions → VS Code + Container Workflow
- Start the stack:
docker compose up --build - In VS Code: Command Palette → Dev Containers: Attach to Running Container
- Select the course container
Useful when you already have JupyterLab open and also want the IDE.
Full instructions → VS Code + Container Workflow
Upload or open the lab notebooks in Colab.
Good for quick experiments when you cannot install Docker.
Full instructions → Google Colab
Preview the MkDocs site without running any labs:
Open http://127.0.0.1:8000
Provisions a cost-controlled set of Google Cloud resources (Cloud SQL + pgvector, GCS, service account, etc.) designed to stay under $50 / month.
cd terraform
cp environments/student.tfvars environments/my.tfvars
# set your project_id
terraform init
terraform apply -var-file=environments/my.tfvars
Vertex AI Vector Search and AlloyDB are disabled by default to protect the budget.
Full instructions → GCP Setup and terraform/README.md
Choosing an environment¶
| Goal | Suggested environment |
|---|---|
| Complete the labs offline | Docker + JupyterLab |
| Debug / develop with a full IDE | VS Code Dev Containers |
| Quick experiment, no local Docker | Google Colab |
| Test against real Cloud SQL / Vertex AI | Docker (or VS Code) + Terraform GCP stack |
| Edit or preview course documentation only | Local MkDocs |
Adding a new environment¶
When a new runtime option is introduced:
- Create a detailed guide under
docs/resources/(e.g.resources/new-env.md). - Add a row to the table at the top of this page.
- Add a new tab (or section) under “Environment details”.
- Update the navigation in
mkdocs.ymlif the new guide should appear in the sidebar.