Deploying Vite
Deploy a static Vite app to Vorynza Host.
Vite apps deploy as static output — Vorynza builds your app once per deployment and serves the result directly from a CDN. There's no server process, so there's nothing to cold-start and nothing to patch.
How it's detected
Vorynza detects Vite from a vite.config.(js|ts|mjs|cjs) file at your repo root, or a vite
dependency in package.json. It sets:
| Setting | Value |
|---|---|
| Output directory | dist |
| Install command | npm install (or your detected package manager's equivalent) |
| Build command | npm run build |
| Runtime | Static |
If your project builds somewhere other than dist, or uses a custom build script, override it
from Settings → Git & build on your app.
What happens on deploy
- Vorynza clones your repo and runs your install/build commands in an isolated build environment.
- The contents of your output directory are uploaded as-is and served from a CDN.
- Your app gets a
*.vorynza.cloudsubdomain immediately — see Custom domains to bring your own.
Because there's no server, requests are served entirely from the CDN edge, and there's no function log stream — only build logs apply to static apps.
Environment variables
Vite only exposes variables prefixed VITE_ to your client code, and — like any static build —
they're inlined at build time via import.meta.env. Set them before triggering a deployment;
changing a VITE_* variable requires a new deployment to take effect. See
Environment variables for how to set and scope them.
const apiUrl = import.meta.env.VITE_API_URL;Client-side routing
If your app uses a client-side router (React Router, TanStack Router, etc.), unknown paths need
to fall back to index.html so deep links and refreshes work. This is handled automatically for
static deployments.