From your terminal
In your app’s folder:https://deals.frogbot.app. The first deploy asks which workspace the app goes in and what to name it; later deploys ship a new version of the same app. Dojo is the default target because of the Dojo plugin, so npx frogbot deploy dojo does the same.
Useful flags, all listed in Deploy to Dojo:
--datauploads your local data with the first deploy, so the app starts with your records and users. Without it the app starts empty.--no-keysskips the question about which keys in your.envto copy into the app’s environment variables.--jsonprints one JSON result, for scripts and coding agents.
From a repo
An app’s Admin can connect it to a GitHub or GitLab repo in the app’s settings: pick the repo, the branch (the repo’s default branch unless you choose another) and the folder the app is in. Dojo adds a webhook to the repo, and every push to that branch deploys. If Dojo loses access to the repo, pushes stop deploying until an Admin connects it again.Follow a build
Every deploy is a deployment with its own build log. The app’s page lists deployments newest first, and the CLI shows them too:Roll back
Open an earlier deployment that went live and choose Roll back. Dojo puts that version back without rebuilding it. Your data stays as it is: a rollback changes the code, not the database.Free previews and paid apps
Each live app takes one paid app on the workspace’s plan. When the workspace has none free, a new app starts as a free preview instead: it runs for a few hours at itsfrogbot.app address, with no custom domain, and stops when the window ends. An ended preview is kept for a week, so you can choose Keep it and pay for it without sharing again. The share prints the upgrade link when a deploy needs one. See Billing.