nnesly
Menu
TRSign in

Deploy SvelteKit

How nesly detects, builds and serves a SvelteKit project — and the two commands that put it on a live URL.

Deploy SvelteKit on nesly

A SvelteKit project is served statically or run as a server, depending on how the project is configured.

cd your-project
nesly deploy --yes

The first deploy creates the project and prints the live URL; after that,nesly deploy is enough.

How detection sees it

  • A package.json depending on @sveltejs/kit is detected as SvelteKit.
  • Only @sveltejs/adapter-static produces a static site (served from build/); every other adapter produces a server, which runs as a container.
  • The first container deploy mints AUTH_SECRET and NEXTAUTH_SECRET (same value) for Auth.js, and sets AUTH_TRUST_HOST so the app trusts the platform edge.

When detection is not what you want, say it yourself: build and start commands, root directory and output directory live in nesly.tomlcommitted next to the code — see builds.

Worth knowing

  • With adapter-node, the server reads PORT from the environment — the platform sets it; do not hard-code one.
  • If you delete AUTH_SECRET, set it again with nesly env set (or redeploy after clearing both AUTH_SECRET and NEXTAUTH_SECRET so a new pair is minted).
  • Attach a managed database withnesly addon add postgres (ormssql) — connection env vars are injected on the next deploy.
  • When a deploy fails, nesly diagnosereads the logs for you and names the fix.

Full walkthrough: get started. Custom domains, backups, GitHub deploys and the rest of the reference: nesly CLI.