Vite deployment
Deploy your Vite app from GitHub.
Connect a supported React, Vue, or Svelte repository. RunYour.App detects the build, accepts the public settings it needs, and publishes the static app on a verified HTTPS route.
- React, Vue, and Svelte
- npm, pnpm, and Bun lockfiles
- Public VITE_* build settings
- SPA routes on direct links
What RunYour.App handles
The supported path is deliberately narrow: one Vite application in a detected app root, a supported lockfile, the default dist output, and a build that completes through the repository’s existing build script.
- Detects the supported framework and package manager from the repository.
- Runs the existing build script, including additional steps already included in it.
- Serves the generated static files through the platform web runtime.
- Falls back to the application entry point for client-side routes and direct deep links.
Existing Docker and web-server files
A repository may contain a reviewed Dockerfile or Docker Compose web-server shape. RunYour.App recognizes supported nginx, Caddy, and Apache source configurations as deployment intent, then uses the same platform static runtime as every other supported Vite SPA.
This is not arbitrary container hosting. Multi-service Compose projects, custom web-server behavior, custom Vite output directories, and runtime-only container images remain outside this profile.
Before you connect GitHub
- Make sure the app builds locally and writes to dist.
- Commit exactly one supported package-manager lockfile.
- Declare only browser-safe VITE_* values; never put a server secret in frontend code.
- Use the separate Express or FastAPI path when the repository must run a server process.