Deploy
Build a bundle, upload it, and serve the new version. `runlot deploy` does all of it.
Use the runlot deploy command to deploy. Builds always run on your own machine, and only the build output is uploaded.
runlot deployHow a deploy works
- Build the bundle. esbuild bundles your entry point and includes the files in the
assetsdirectory. - Check the project. If the project does not exist yet, it is created.
- Upload. A gzip-compressed tar file is uploaded.
- 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.assetsand the assets directory
Managing deploys
Runtime and limits
- Bundle rules — compatibility flags, wasm, size limits
- Stop and resume — automatic shutdown when there are no requests, and resume
- Cold state and resume — reactivating a project that has been inactive for a long time