Skip to content

Start with the path that matches the work

Beampipe can be explored locally without touching scientific infrastructure, connected to an existing DALiuGE service, or prepared for scheduler-backed production. Choose the boundary you need to cross today.

SAFE / MOCK

Prove the control plane locally

Start PostgreSQL, install the WALLABY configuration, run diagnostics, and open the real operator console. Archive, scheduler, and DALiuGE calls stay disabled.

Run the five-minute start

The safe progression

Do not skip from installation to live submission. Beampipe makes external uncertainty explicit; the setup path should do the same.

Local command deck

docker compose up -d postgres
mkdir -p operator-local
beampipe init --directory operator-local
cd operator-local
beampipe setup --yes \
  --admin-password 'replace-this-local-password' \
  --project-config ../config/wallaby_hires.v2.yaml
beampipe doctor
beampipe start

The setup command writes private local configuration, applies migrations, creates the administrator, installs a deployment profile, validates the project, and runs diagnostics. It refuses to replace a different profile silently.

You need to Continue with
Understand prerequisites and release artifacts Installation
Complete one source-to-execution workflow First workflow
Explain an environment variable or precedence rule Application configuration
Start an operator shift Operator handbook
Understand why Beampipe owns state but not science execution Architecture map