Skip to main content

Deployment

Environments​

Since 23 October 2026, both Suite environments run as standalone Node servers on Oracle Cloud VMs:

EnvironmentPublic origin
Productionhttps://suite.sabrobotix.com
Shared testhttps://suite-test.sabrobotix.com

Each VM has its own SQLite database, configuration and systemd suite service. The old Suite Workers and D1 databases were deleted. DNS, Cloudflare Tunnel, vehicle SSH Access and R2 object storage remain on Cloudflare. The documentation site has its own Worker deployment; it is independent of the Suite application.

Production delivery​

Every push runs .github/workflows/tests.yml: lint, typecheck, model and integration tests, lockfile validation, the standalone Node build, accessibility and documentation checks.

A successful Tests run on main starts production.yml. It checks the production database schema before creating the semantic release, verifies the release tag, version and changelog, checks out that exact release commit, repeats the code checks and deploys with deploy/node/deploy.sh prod. The server installs the release only when its health check succeeds. The workflow then verifies the public health endpoint, home page and OIDC flow.

Manual deployment, from the repository root in macOS Bash or Windows Git Bash:

deploy/node/deploy.sh test
# Production recovery, after the required code checks:
deploy/node/deploy.sh prod

SSH access, VM addresses, rollback and server provisioning are documented in the repository's internal docs/oracle-production.md runbook. There is no deploy.yml recovery workflow.

Build settings​

Scripts npm run build and npm run node:build produce .next/standalone for the production origin; npm run build:test selects the Oracle test origin. Both public builds default LTE/video flags to true and force NEXT_PUBLIC_ENV=prod; npm start and npm run node:start start it. These npm commands work in Windows and macOS shells.

The deploy script supplies the correct NEXT_PUBLIC_SITE_URL and enables NEXT_PUBLIC_DRONE_CONTROL_LTE_ENABLED and NEXT_PUBLIC_DRONE_VIDEO_MEDIAMTX_ENABLED. These are build-time values: changing a service environment file cannot change the browser bundle.

Both public environments use NEXT_PUBLIC_ENV=prod. The value test enables local testing shortcuts and must never be used in a public build.

Secrets and data​

Runtime settings and secrets come from /etc/suite/suite.env, read by the Node service. OIDC_ISSUER and JETSON_SUITE_ALLOWED_ORIGINS must use the environment's public origin. SQLite lives at SUITE_DATABASE_PATH; R2 is reached through the S3 API configured by R2_* variables.

Migrations are manual, before deploying code that needs them. Apply them to test first, take an online SQLite backup, then apply each migration and its d1_migrations ledger entry in one transaction. The ledger name is retained for compatibility; it does not imply a D1 database. npm run db:check-schema -- --sqlite <file> verifies a local copy. The release and daily database-schema.yml workflow inspect production through the restricted Oracle backup connection.

See Node server settings and the internal docs/oracle-production.md and docs/database-restore.md runbooks. The former Workers CPU limit no longer applies to the Suite service.