Deploy

Use the runlot deploy command to deploy. Builds always run on your own machine, and only the build output is uploaded.

runlot deploy

How a deploy works

1. Build the bundle. esbuild bundles your entry point and includes the files in the assets directory.
2. Check the project. If the project does not exist yet, it is created.
3. Upload. A gzip-compressed tar file is uploaded.
4. Activate the new version. Once the new version is ready, traffic is routed to it.

When it finishes, the version number and the deploy URL are printed.

Related pages

Basics

• runlot deploy — the command and its output
• Deploy URL — how the address is decided
• Static assets — env.assets and the assets directory

Managing deploys

• Versions and rollback
• Secrets
• Logs

Runtime and limits

• Bundle rules — compatibility flags, wasm, size limits
• Stop and resume — automatic shutdown when there are no requests, and automatic restart on the next one
• Cold state and resume — reactivating a project that has been inactive for a long time