Praecise Deploying and rolling back
What happens when you deploy on Praecise Cloud, and how an earlier release is served again.
A deploy turns a folder or repository into a checked release behind the edge. An earlier release can be served again.
In short
A deploy detects and builds the source, places it behind the edge and checks it before it takes traffic. Recent releases are kept, and any one can be served again. This page is for anyone deploying a project.
What a deploy does.
3
Build
Detect and build.
Praecise works out whether the source is a static export, a Node app or a container image, and builds it.
Place
Put it behind the edge.
Routing and certificates are in place before the release serves traffic.
Operate
Check, then serve.
Health is checked before a release takes traffic, and the release id names what was placed.
Deploy from the Cloud section of Praecise Spaces.
3
A registered source
Repository and branch.
A project with a registered repository and branch is deployed from the Deploy button.
No source registered
The button says so.
A project without a registered source has the button disabled and explains why.
Environment settings
Kept beside the site.
Settings are kept outside every release, so a redeploy does not disturb them.
Rolling back.
3
Kept
Recent releases stay.
Each release is named by its id, and recent ones are kept.
Serve
Any kept release can be served again.
Praecise waits for the site to be healthy before it takes traffic.
Settings
A rollback carries no settings.
Environment settings stay beside the site, so they are the same before and after.
What can be deployed.
4
A static export
Files served behind the edge.
A Node app
Run behind the edge, with settings kept outside the release.
A container image
An app that ships as a container image is run from the image.
A Harness app
A Node app that is also a chat page, a REST API and an MCP endpoint.
Next pages.
06
Praecise accounts are by invitation. Open the console, or talk to us.
New to Praecise Cloud? Accounts are set up with the Praecise team: talk to us, then sign in to the Cloud section of Praecise Spaces with an email code.
Written and kept by Praecise Cloud. Read from https://praecise.cloud/docs/deploying.md.