Static Sites
FluxNow can deploy static site output directly to CDN-backed hosting, without a running server process.
Auto-detection
Section titled “Auto-detection”FluxNow detects static output if your repository produces a standard build output directory:
dist/out/build/public/
If detected, the project is configured as a static site automatically. You can also enable static hosting manually in the review panel during import, or after the initial deploy from Settings → Services in the project dashboard.
Build configuration
Section titled “Build configuration”Configure in the project dashboard:
- Build command — the command that produces your static output (for example,
bun run buildornpm run build) - Output directory — the directory containing the built files (for example,
dist)
Preview environments
Section titled “Preview environments”Each pull request preview gets its own static preview URL. The static output is built from the PR branch and deployed independently from staging.
Cache invalidation
Section titled “Cache invalidation”Every deploy triggers a full cache invalidation for your project’s CDN distribution. Visitors always get the latest version immediately after a deploy completes.
Custom domains
Section titled “Custom domains”Static sites support custom domains. Attach a domain from the project dashboard and FluxNow handles TLS provisioning automatically.