arcflow migrate up

Apply embedded PostgreSQL schema migrations shipped in runtime/arcflow-core/migrations/. Required before arcflow-server can serve POST /v1/runs on a fresh database.

Usage

export ARCFLOW_POSTGRESQL_URL=postgres://arcflow:arcflow@localhost:5432/arcflow
arcflow migrate up

Subcommand structure:

arcflow migrate up

(No additional flags today.)

Expected output

Success:

[ArcFlow] migrations applied.

Failure examples:

[ArcFlow] ARCFLOW_POSTGRESQL_URL must be set for migrate up.
[ArcFlow] postgres connect failed:...
[ArcFlow] migration failed:...

Exit codes

Idempotent behavior

Migrations use IF NOT EXISTS and version tracking inside arcflow_core::migrate::run. Re-running migrate up on an up-to-date database succeeds without changes.

Seven migrations

Table detail: server/postgres-schema.md.

Deploy runbook

Option A: CLI before server rollout

export ARCFLOW_POSTGRESQL_URL=...
arcflow migrate up
# deploy arcflow-server
curl -sf https://api.example.com/ready

Option B: Docker Compose init container

docker/docker-compose.server.yml runs arcflow-migrate once Postgres is healthy, then starts the server.

When to prefer manual migrate

• Blue/green deploys where DB migrates in a separate job
• CI gates that fail deploy if schema drift detected
• Managed Postgres where init containers are not used

Verify after migrate

curl -s -o /dev/null -w "%{http_code}\n" http://localhost:8080/ready

Expect 200. 503 indicates connection failure or pending migrations.

Related pages

• server/postgres-schema.md
• server/overview.md
• cli/overview.md