URL scheme
Rules the form enforces:
- Env values are never accepted from a link, only the names. The visitor types each value, and it is stored as a secret.
- A parameter that fails validation is ignored, and a banner names every ignored parameter. Unknown parameters are ignored the same way.
- The form shows “Prefilled from a link: review before deploying” and names the source host when
sourceis valid. - If the link has no valid
image, the regular new app wizard opens with the banner above it.
Launcher page
Most READMEs should link to the launcher, because the author does not know the visitor’s server:localStorage in that browser only, validates that it is an http or https address without a username or password, then redirects to <server>/apps/new?deploy=1&... carrying the same parameters. It makes no external requests and has no tracking. It does not add deploy=1 to the link you write, the launcher does that.
Badge
The badge is a flat SVG that reads on light and dark backgrounds:traefik/whoami, port 80, health path /health):
: / and , inside parameter values as shown. For a project that needs secrets, add env=API_KEY,DATABASE_URL.
Generate a link from the CLI
--server https://levelrail.example.com to also print the direct link for one specific server, or --launcher URL to point at a self-hosted copy of the launcher. See the CLI reference.
Self-hosting the launcher
deploy.html and deploy.js are plain static files under docs/public. Copy both, plus badges/, to any static host and pass that host to --launcher.