Skip to main content

miren deploy

Deploy an application

Deploy uploads your source, builds a new container image on the server, and activates the resulting version — replacing the previously running one. This is the only command that rebuilds your image.

To activate a previously built version without rebuilding, pass --version:

miren deploy --version myapp-vCVkjR6u7744AsMebwMjGU

This reuses the existing image and rolls it out immediately — useful for rolling forward to a known-good version without waiting for a build. Find version IDs with miren app history.

Config changes deploy on their own

Changing environment variables (miren env set / miren env delete) or addons (miren addon create / miren addon destroy) already creates and rolls out a new version. You only need miren deploy when your code or app.toml has changed.

Usage​

miren deploy [flags]

Flags​

  • --analyze — Analyze the app without building (show detected stack, services, etc.)
  • --env, -e — Set environment variable (KEY=VALUE, KEY=@file, or KEY to prompt)
  • --ephemeral — Deploy as ephemeral preview with this label (e.g. feat-login)
  • --explain, -x — Explain the build process
  • --explain-format — Explain format (default: auto) (choices: auto, plain, tty, rawjson)
  • --force, -f — Skip confirmation prompt
  • --sensitive, -s — Set sensitive environment variable (masked in output)
  • --summary-json — Write a JSON summary of the deploy result (deploy id, version, and route URLs) to this path
  • --ttl — TTL for ephemeral version (e.g. 48h) (default: 24h)
  • --version, -V — Deploy an existing version (skip build)

Config Options​

  • --cluster, -C — Cluster name
  • --config — Path to the config file

App Options​

  • --app, -a — Application name
  • --dir, -d — Directory to run from (default: .)

Global Options​

  • --options — Path to file containing options
  • --server-address — Server address to connect to (default: 127.0.0.1:8443)
  • --verbose, -v — Enable verbose output

Examples​

Basic:

miren deploy

Analyze:

Before deploying, the system can tell you how it's going
to treat your application by running:

miren deploy --analyze

Set environment variables during deploy:

miren deploy -e DATABASE_URL=postgres://localhost/mydb

Deploy a previously built version:

miren deploy --version v3

Subcommands​