Deploy SvelteKit on Your Own Server

Deploy SvelteKit applications with server-side rendering, API endpoints, and form actions using the Node adapter.

Quickstart

From your project root, deploy with your preferred package manager:

npx @temps-sdk/cli up

Temps detects your svelte.config.js, runs npm run build, and starts the Node.js server. Your app is live in about 2 minutes.

Node Adapter Setup

SvelteKit requires the Node adapter for production deployments on Temps:

npm install -D @sveltejs/adapter-node

// svelte.config.js
import adapter from '@sveltejs/adapter-node';

export default {
  kit: {
    adapter: adapter()
  }
};

What Temps Handles Automatically

Environment Variables

npx @temps-sdk/cli environments vars set DATABASE_URL "postgres://..." -e production

npx @temps-sdk/cli environments vars set SECRET "your-secret" -e production

Public variables use the PUBLIC_ prefix in SvelteKit and are embedded at build time.

Platform behavior

These rules apply to every app deployed on Temps, regardless of framework.

Health checks

After your container starts, Temps sends HTTP GET requests to verify it is healthy before routing traffic to it.

• Path: / (the root of your application)
• Success: 2 consecutive responses with a 2xx or 3xx status code
• Timeout: 300 seconds (5 minutes) for the app to become healthy
• Retry interval: every 5 seconds

Connection errors while the app is still starting are retried without penalty. If the app returns 4xx or 5xx errors for 60 consecutive seconds, the deployment fails. Customize the check by adding a .temps.yaml to your repository root:

health:
  path: /health
  status: 200
  interval: 30
  timeout: 5
  retries: 3

Auto-injected environment variables

Temps injects these variables into every deployment automatically:

You do not need to configure these manually. They are available in process.env (Node.js), os.environ (Python), os.Getenv (Go), and the equivalent in other languages.

Next Steps