Fakturaflyt

Architecture

How Fakturaflyt (https://fakturaflyt.pages.dev) is built, where its demo data lives, and how it ships.

Platform: Cloudflare Pages (Vite SPA)Branch: masterOutput: dist/

Request path

  1. Landing page and demo in one Vite SPA (React + React Router). There is no backend: every demo step runs in the browser.
  2. The edge serves index.html and hashed assets; client routing takes over for /, /demo and the /* fallback (public/_redirects).
  3. Demo EHF-XML is generated locally with the vendored ehf-helper copy and stays in the browser until downloaded. The only network call the app itself makes besides the configured lead-form POST is the optional Cloudflare Web Analytics beacon.

Data and state

Background work

Surfaces

Public URLhttps://fakturaflyt.pages.dev
Sourcegithub.com/bergvictor/fakturaflyt
Routes/, /demo, /architecture.html (also /architecture), /ehf-sjekkliste.html; unknown paths serve /index.html with HTTP 200.
DeployVite builds src/ to dist/; public/ is copied verbatim and deploys with project fakturaflyt.

Ship it

npm ci
npm run build
git push origin master
# wait for the Cloudflare Pages production build, then:
python3 scripts/check_build_json.py --url https://fakturaflyt.pages.dev --expected-revision <full-SHA>