Preview Environments

FluxNow creates a fully isolated preview environment for every pull request you open against your default branch.

How previews work

When a PR is opened, FluxNow:

1. Builds a new container image from the PR branch
2. Provisions an isolated environment in its own namespace
3. Posts the preview URL to your dashboard and as a PR check

The preview URL is unique per PR and available as soon as the build completes.

Services in preview environments

• Postgres — each preview gets its own database, with the schema branched from staging
• Redis — not provisioned per preview; preview pods are not wired to a Valkey instance
• S3 — not provisioned per preview; there are no per-PR buckets, so a preview can never touch your staging objects

Only Postgres is branched per preview today. Redis and S3 are provisioned for staging (and production) only.

Environment variables

Preview environments use the same environment variables as staging (from your fluxnow.yaml).

Disabling previews

To turn preview environments off for a repo, set preview.enabled: false in fluxnow.yaml.

Lifecycle

• Preview environments are created when a PR is opened or when a new commit is pushed to an open PR.
• They are deleted automatically when the PR is merged or closed.
• Preview environments are not intended for production traffic — no custom domain support, and storage is ephemeral.

Preview URL format

Preview hostnames follow the pattern <customer>-<app>-pr-<pr-number>.openfab.dev — for example, acme-api-pr-42.openfab.dev. This is the same host that refs resolve to in previews, so sibling apps in a monorepo reach each other’s matching preview automatically.

The exact URL is posted as a check on the pull request.