Deployments

FluxNow deploys are driven entirely by branch activity. There is no manual deploy button.

Staging deploys

Any push or merge to your default branch (main or master) triggers a staging deploy automatically.

Deploy process

1. Build — FluxNow builds a container image from your repository using the configured build strategy (Dockerfile or Railpack).
2. Push — the image is pushed to the FluxNow container registry.
3. Migrate — if a migration command is configured, it runs as a pre-deploy step before traffic switches.
4. Rolling update — the new image rolls out in Kubernetes with zero-downtime deploys. Old pods stay running until new ones pass health checks.

Migration handling

You can configure a migration command in the project dashboard (for example, bun run db:migrate). The command runs inside your container image against the staging database before the new version receives traffic.

Caution

If the migration command exits non-zero, the deploy is halted and the previous version stays live. Migrations should be idempotent and backwards-compatible with the running application version.

Zero-downtime deploys

FluxNow uses Kubernetes rolling updates. The old version continues serving traffic until the new pods are healthy. There is no maintenance window.

Deploy history and logs

The project dashboard shows a full list of deploys with status, timestamps, and streaming build and runtime logs per deploy.