deploy
The deploy tool runs check, builds the UI and the backend, updates the schema and puts the UI and the API live at <id>.manh.run together; it is the only call that changes the running app.
deploy
- Parameters:
project.force: deploy even though TypeScript reports type errors or a page fails to render. Syntax, gate and contract errors can’t be overridden.reason(required withforce, 5–300 characters): why those type errors don’t break the app. manh.run keeps it on the deploy record.
- Returns:
handover: whether the app is ready to hand over. With failing tests or work left it saysNOT READYplus what the agent must do now, before replying to you.tests: the results of the tests run on the test copy (passed,total, the failing ones).- the deploy result (schema notes, cron jobs registered, whether check was skipped), the app’s addresses, the Progress section and a
nextstep.
- When the agent calls it: once the API phase passes check, to test the real API; and when the app is done.
The /directory URL has no force or reason.
What a deploy does
- Check. Runs all four layers, types included. Any error returns
CHECK_FAILEDwith the list; the running app stays as it was. - UI. Compiles every
.tsxfile into static files. Each static route gets its own HTML carrying that page’sexport const meta. A compile error returnsfile:linebefore anything changes. - Backend. Bundles every backend
.tsfile into one module. Bundle errors returnfile:linetoo. - Schema. Tables from
*.table.tsare applied to the app’s own database when the new version starts. Tables and columns are only added, never dropped or retyped. - Go live. The UI and the API switch to the new version together.
deploywaits until the new version answers, usually 3–10 seconds; the first deploy takes longer. - Test. Runs the tests in
spec/acceptance.json(or, until it exists, smoke tests manh.run makes from your files) on a test copy with its own database, for about 30 seconds. Live data is never touched. See Testing.
A file tree that deployed successfully before skips the check step (the result says gate: "known_good"). That way restore_checkpoint followed by deploy always rolls back, even after check gains new rules.
https://<id>.manh.run/ UI
https://<id>.manh.run/api/* API (app/orders/get.ts = GET /api/orders)Next steps
- Deploy your app: deploying from the dashboard and what goes live.
- check: the check layers.
- Rollback and checkpoints: going back to an earlier version.
Last updated