Instance bootstrap

Before you can open Tour de contrôle → Documentation (/docs), you must install the Portlane Cœur on your Linux server. Internal runbooks are served only from a running Activation.

1. Espace client

1. Sign in at app.portlane.io
2. Open Licence — download your Organisation's signed Licence file (Licence à vie model; no seats)
3. Open Téléchargements
4. Download the Cœur bundle (portlane-core-*.zip) — the full suite of seven moteurs
5. Optionally download Flux — empty repository scaffold to initialize portlane-flux
6. Optionally download RPA — complementary module
7. Click Obtenir le token GHCR — copy username and token for Docker login

Download is self-service once your Organisation has been activated commercially. If you do not see an active Licence, contact BastionLab.

The zip is stored in a private Supabase bucket; the Espace client generates a 15-minute signed URL.

2. Verify and configure

On the target VM (Ubuntu 24.04 LTS recommended, 8 GB+ RAM):

unzip portlane-core-V.zip && cd portlane-core-V
sha256sum -c checksums.sha256
# Place the Licence file you downloaded from the Espace client in this directory before install
cp deploy/.env.example deploy/.env
cp deploy/publish.env.example deploy/publish.env
# Edit deploy/.env (passwords) and deploy/publish.env (target URLs for your flux)

3. Authenticate and install

echo "$GHCR_TOKEN" | docker login ghcr.io -u "$GHCR_USER" --password-stdin
./install.sh

Offline / air-gapped: the bundle may include deploy/images.tar — use ./install.sh --offline.

install.sh installs Docker if needed, pulls pinned images, starts seven moteurs + docs, and initializes the embedded portlane-flux/ git scaffold (empty Flux project).

All moteur images come from a private GHCR registry, signed and pinned to exact versions in the bundle: your Activation runs exactly what was released, and a registry tag changing later never silently updates a server. Day-to-day flux deployments follow the same pull model — see Developer setup.

4. First access

Use the viewer credentials from deploy/.env for Basic auth.

5. Connect your Flux repo

The bundle includes a starter portlane-flux/ folder (empty scaffold). Point it to your Git remote:

git -C portlane-flux remote add origin <your-github-url>
git push -u origin main
git -C portlane-flux checkout -b dev && git push -u origin dev

See Developer setup for the dev/prod CI model.

Automation (ops)

Headless equivalent of the Espace client download (requires Supabase service role):

export SUPABASE_URL=... SUPABASE_SECRET_KEY=...
./deploy/scripts/fetch-client-bundle.sh --version 0.0.0-test --output /opt
./deploy/scripts/bootstrap-instance.sh --bundle-dir /opt/portlane-core-0.0.0-test

Full sandbox runbook lives in on-prem docs after install: Bootstrap instance dev.

Next steps