Deployment

Andurel v2 builds generated database code, email styles, Templ components, CSS, optional Inertia assets, and the Go web application.

Build

1andurel build --version v2.0.0-dev

The command runs narsilc when query files exist, compiles email templates, generates Templ code, minifies Tailwind CSS, installs frontend dependencies and builds Vite assets for Inertia projects, downloads Go dependencies, and compiles the application release.

The JavaScript package manager comes from andurel.toml. It is independent from the Node runtime used by cmd/ssr.

Deploy process types

andurel build produces the web application from cmd/app. Build the queue and SSR entry points separately when the application uses them:

1CGO_ENABLED=0 GOOS=linux go build -o orbit-queue ./cmd/queue
2CGO_ENABLED=0 GOOS=linux go build -o orbit-ssr ./cmd/ssr

Deploy these as separate process types. They may share a database and telemetry backend, but each owns its Fx lifecycle and shutdown. cmd/ssr still needs a Node runtime for the SSR bundle even when the Go wrapper owns process lifecycle.

Apply root migrations/ as a deliberate release step before traffic reaches code that needs the new schema. Back up important data before destructive changes.

Environment and health

Provide production database, HTTP, session, auth, email, queue, telemetry, and optional Inertia SSR settings through the deployment environment. Set ENVIRONMENT=production so secure cookie and server policies apply.

The storage health check verifies the database. Configure the platform's startup and liveness checks to cover required dependencies and allow enough termination time for HTTP requests and queue jobs to stop cleanly.

Development releases

The current master branch is the v2 development line. Pin the CLI commit and the independent package versions in go.mod for reproducible pre-release deployments. Do not treat the stable v1 @latest tag as v2 until v2.0.0 is published.