Skip to main content
Deployments are associated with a project revision and a hosting target. The normal lifecycle is:
  1. Build and validate a revision.
  2. Create a preview deployment.
  3. Verify the application, configuration, and integrations.
  4. Promote or create a production deployment.
  5. Monitor status and roll back through the supported project workflow when necessary.
P2HS provides managed deployment, routing, and domain services. The exact target behavior depends on the project configuration and deployment options available to the workspace.

​
Environment separation

Keep preview and production configuration separate. Environment variables and secrets are project-scoped policy-controlled assets; their allowed propagation target must be explicit.