Skip to content
Damvia

Client build

The client is a Vite single-page application. npm run build produces a dist/ folder of static files that any web server, CDN or object storage website endpoint can serve. There is no client Dockerfile or hosting configuration in the repository.

Build

Section titled “Build”

The client’s package.json depends on the server package for types, so both must be installed:

Terminal window
cd server && npm install
cd ../client && npm install
cp .env.template .env      # then set VITE_API_ENDPOINT
npm run build

Set VITE_API_ENDPOINT to the public API URL followed by /trpc, for example https://api.dam.example.com/trpc, and the brand colours if you use them. Vite reads client/.env at build time; the values are compiled into the bundle, so a different API URL means a different build.

npm run build runs vite build only; type-checking is not part of it. Run npx vue-tsc --noEmit first if you want a type error to fail the build.

The output is client/dist/: an index.html, hashed assets under assets/, and favicon.svg.

Serve with a history fallback

Section titled “Serve with a history fallback”

The router uses HTML5 history mode, so /collections/abc must return index.html from the server rather than a 404.

nginx:

server {
  listen 443 ssl;
  server_name dam.example.com;
  root /srv/damvia/client/dist;


  location / {
    try_files $uri $uri/ /index.html;
  }


  location /assets/ {
    add_header Cache-Control "public, max-age=31536000, immutable";
  }
}

Caddy:

dam.example.com {
  root * /srv/damvia/client/dist
  try_files {path} /index.html
  file_server
}

Netlify, Vercel, Cloudflare Pages and S3 static websites each have a rewrite or “SPA fallback” setting that does the same.

Caching

Section titled “Caching”

Files under assets/ carry a content hash in their name and can be cached forever. index.html must not be cached aggressively, or users keep loading an old bundle that references deleted hashed files after a deploy.

Fonts

Section titled “Fonts”

index.html loads Inter from Google Fonts. A locked-down network or a strict Content Security Policy needs the font self-hosted; see Branding.

Same host or separate host

Section titled “Same host or separate host”

The client and the API can share a hostname (proxy /trpc and /v1/ to the server, everything else to the static files) or use two hostnames. Both work because the API’s CORS allows any origin and the session travels in an authorization header rather than a cookie. Example configurations are in Reverse proxy.