Guides
Deploy
Upload the project file tree — schema, APIs, and frontend — to Starbase.
From a linked project folder:
The CLI reads .robodev, collects the allowed file tree (database.ts, api/**/*.ts, jobs/**/*.ts, index.html, src/**, and config files), and POSTs them to /v1/projects/:id/deploy. When .robodev has a frontend object, it also runs the local package.json script (default build) in that root and uploads the text output as index.html + public/**. frontend: false skips that build. Starbase compiles APIs, jobs, and the hosted UI, syncs the schema, and serves the app on the project host. The dashboard Code page Save uses the same API and does not run Vite.
Destructive changes
If the plan would drop tables or columns, deploy returns 409. The CLI prints the SQL and asks for confirmation. Skip the prompt with --force.
Project hosts
- https://{projectId}.robodev.povio.dev.
Wait until live
After Starbase accepts the deploy, the CLI waits until the public project host is reachable and the tenant database accepts a connection (up to 30 seconds). Then it prints the App URL, Docs URL (/_robodev/docs), schema operations, and registered routes.
If the host does not become reachable in time, the command exits with an error. The deploy was accepted, but the CLI does not print Deployed to ….