Static Site - Replov Docs
Skip to main content

Static Site

Static projects built into an Nginx container

Replov builds supported static projects in Docker, copies the generated files into a pinned Nginx runtime image, and exposes the container through the same Traefik ingress used by web services.

Supported projects

  • Raw HTML — index.html at the selected root; output .
  • Vite / Vue / Svelte — build script; output dist
  • Create React App — build script; output build
  • Angular — build script; output angular.json outputPath
  • Astro — build script; output dist
  • Flutter Web — pubspec.yaml and web/index.html; output build/web
  • Gatsby — build script; output public
  • Next.js static export — next.config output: 'export'; output out
  • Nuxt generate — nuxt/nuxi generate script; output .output/public or dist
  • SvelteKit static — @sveltejs/adapter-static configured; output build
  • Hugo — Hugo config; output public
  • Jekyll — Gemfile, _config.yml, and a lockfile or exact Jekyll version; output _site
Server-rendered frameworks
Next.js without output: 'export', Nuxt without a generate script, and SvelteKit without adapter-static require a Web Service. Express, Remix, NestJS, and other server runtimes also require a Web Service.

Build requirements

Node projects need the framework's build/generate script or a build command supplied during service creation. Replov detects the lockfile and uses npm, pnpm, Yarn, or Bun. An optional Publish Directory override is available for non-standard output paths.

package.jsonjson
{
"scripts": {
"build": "vite build"
}
}

Every generated output must contain an index.html. Builds fail before release when the configured directory or entry file is missing.

Deploy Flutter Web

  1. Commit a Flutter project containing pubspec.yaml and web/index.html to GitHub.
  2. Create a Static Site, select the repository and branch, and set Root Directory to the Flutter app folder (or / when it is at repository root).
  3. Declare the supported Dart and Flutter SDK ranges under environment in pubspec.yaml. Replov selects the newest compatible stable SDK.
  4. To require one exact Flutter release, commit .fvmrc, .flutter-version, or a Flutter entry in .tool-versions.
  5. Leave Build Command empty for the standard release build, or configure a service-specific command with --dart-define or --dart-define-from-file. Replov still verifies build/web before publishing.
  6. Create separate services for development and production. Each service can follow its own branch and Flutter build command from the same repository.
Replov generated buildbash
flutter pub get
flutter build web --release
# Production service example:
flutter build web --release --dart-define-from-file=config/production.json
# verified output: build/web/index.html
Flutter Web configuration is compiled into files sent to every browser. Do not place private API keys, passwords, or server credentials in --dart-define files.

Routing and HTTPS

Nginx serves assets on port 80 inside the container. Traefik provides the public route, custom-domain routing, and TLS. Browser routes fall back to index.html for single-page applications, while missing asset files remain real 404 responses.

Static sites are not currently delivered through a global CDN. Deploying a new version replaces the running service, so a brief interruption is possible.