Skip to Content

Deploy

≈ 5 min · you will have the app live at <id>.manh.run, with the UI and the API on the same version.

One deploy runs check, builds the UI and puts the UI and the API live together. With errors left, manh.run refuses and the running app stays as it was.

Writing files never deploys. The app’s users see a new version only when someone deploys, so they never meet a half-written one.

Deploy

Two ways, one process:

  • Tell the agent: “Run check, then deploy the Purchase requests app.” The agent calls the deploy tool.
  • Select Deploy at the top of the project page in the dashboard.

Each deploy saves a checkpoint, runs check, builds the UI, puts the UI and API live, then updates the database schema and the cron schedule. Then manh.run runs the app’s tests on a separate copy (live data is never touched) and returns the results to the agent. If a test fails, the agent fixes the app and deploys again.

The app’s address

k7xq2mfp9dhw.manh.run/ UI (/, /requests, …) k7xq2mfp9dhw.manh.run/api/requests the app's API

The UI and the API share one address and are always the same version. Before the first deploy, the address shows the preview and the API answers 503.

Good to know

  • The agent should deploy once the API is done, to test it with real data, and again when the UI is done.
  • Rolling back changes the code, not the data.

Next steps

Last updated