Deploy guide · runtime = "docker"
Deploy Solid on Percher
Solid.js is a JSX framework with fine-grained reactivity and no virtual DOM. The SPA on Vite ships on Percher the same way every other Vite SPA does — multi-stage Docker, Caddy-served static bundle.
Why Percher fits
- Solid's compile-time reactivity means very small runtime bundles — the slim Caddy image plays into that on the serving side.
- Standard `VITE_*` env-var auto-forwarding; no Solid-specific platform shims.
Quick start
bunx percher create my-app --template solid
cd my-app
bunx percher publishThe first command scaffolds a working Solid project plus a `percher.toml`. Publish builds and deploys it; the live URL prints on completion.
percher.toml
The canonical config for a Solid app on Percher. `bunx percher init` generates this automatically when it detects Solid in your project.
[app]
name = "my-app"
runtime = "docker"
framework = "solid"
[web]
port = 8080
health = "/"
Common gotchas
- SolidStart (the fullstack framework) is a different shape — for the SSR variant, use the Node runtime instead. The Solid template here is the SPA variant.
- Hot reload and prod build are separated cleanly in Vite; the deployed bundle won't include dev-only code paths.
Related docs
Ready to deploy Solid?
Free plan, no credit card. Live in under a minute.
Sign up free