Running locally
Run your app locally before you deploy. The local stack runs the same components as the deployed environment.
The local development stack runs the control plane, the node agent, and the front on a single machine. It uses the same components as the deployed environment, so you can confirm behavior locally first.
runlot-admin dev upAfter starting the dev stack, point the CLI at your local control plane.
export RUNLOT_API_URL=http://127.0.0.1:8080
runlot login <name>Without RUNLOT_API_URL the CLI targets production (https://dash.runlot.io). Keep the variable in your shell while you work against the local stack.
runlot login <name> is a login method available only on a dev server. It signs you in as the account with the given name without going through a browser. Reusing the same name signs you back into the existing account.
This login path is not offered in production. The login screen only shows the login methods the server has enabled, so this field does not appear there at all.
Deploying uses the same command
runlot deployProjects deployed to the local stack get a URL too. Locally it is shown in the form http://<host>:8787.
Switching between stacks
Login credentials are stored per control plane URL. Changing the target with RUNLOT_API_URL or --api never uses another host's token.
runlot versions --api https://api.runlot.ioNot available yet
next dev does not support runlot bindings. See Frameworks for how to set up a Next.js app.