Kuma Mieru Docs
Deploy

Choose a Deployment Method

Compare the support status of each deployment method and how configuration changes apply, then select one.

Before you deploy

  • Get the full URL of an Uptime Kuma status page, for example https://example.kuma-mieru.invalid/status/default.
  • Set the Uptime Kuma display time zone to UTC+0.

For the procedure, see Connect Uptime Kuma.

Deployment methods

Platform root directory

The repository is a monorepo, and the web application is in apps/web. When you import the repository on Vercel, EdgeOne Pages or Cloudflare, set the project root directory (Root Directory) to apps/web. On Netlify, set Package directory to apps/web; see Netlify. The platform configuration files vercel.json, netlify.toml, edgeone.json and wrangler.jsonc are in this directory.

When the configuration applies

The web application generates its configuration with the generate script. The script reads the environment variables, requests each status page to get its title, description and icon, and writes the result to apps/web/config/generated-config.json. Each deployment method runs this script at a different time. Thus the action after you change an environment variable is also different.

Deployment methodConfiguration is generatedAfter you change a variable
Vercel, Netlify, EdgeOne PagesDuring the platform buildRedeploy
DockerWhen the container startsRecreate the container
Run from sourceWhen you run bun run dev, bun run build or bun run startRun the command again

Some variables apply at a different time. See Environment Variables.

Last updated on