Recipes

Worked project setups you can copy and adapt. Each recipe is a separate page with a use case and an explanation of every project setting it uses.

What's in each recipe

A use case plus every setting, explained.

A concrete use case.
Setting-by-setting explanation of what it solves and how it works.
Why named services, process commands, browser sessions, and setup scripts are configured a specific way.
Docker-specific operational guidance where relevant.

Index

Single-repo frontend running directly on host with a Spaces-managed named service on a stable per-workspace URL.

Single frontend service in Compose, with workspace-isolated named services on stable per-workspace URLs and notes on stop vs down.

Frontend and backend processes from one repo, each a dedicated named service on its own stable per-workspace URL.

Containerized full-stack setup with named services on stable per-workspace URLs.

Cross-project pattern using workspace overrides to run both services in one context.