The life of a deployment
A deploy is a build and the artifact it leaves behind. Preview and production run the same pipeline, and moving a build from one to the other never rebuilds it.
Preview and production
naro deploy builds a preview. naro deploy --prod builds production. Both resolve to a predictable URL.
- Preview
https://<name>-preview.naro.sh- Production
https://<name>.naro.sh
naro deploynaro deploy --prodDeploy on every push
naro git connect links a repository — it defaults to your origin remote — and every push to the default branch deploys. naro git disconnect stops it.
naro git connectPromote a preview
naro promote republishes a build's stored artifact to production. It does not rebuild, so only a READY deployment that still has its artifact can be promoted.
naro promote <deployment-id>Roll production back
naro rollback restores the newest production build serving a different artifact than the current one. Comparing artifacts rather than row order keeps repeated rollbacks from bouncing between the same two builds.
naro rollbackBuild cache
The framework's cache directory is carried between deploys of the same branch, so an unchanged build does not start from nothing.
Look at one deploy
naro deployments lists them. naro inspect shows one, with its build logs.
naro deploymentsnaro inspect <deployment-id>