Skip to Content
OperationsDeployments

Deployments

The inspection app deploys through Vercel. Preview and production environments use different database and Salesforce settings, so deployment notes must always state which environment is being discussed. This page exists because the app can write to Salesforce, and confusing preview, sandbox, production databases, or production Salesforce credentials can create real operational errors.

Inspection app deployment model

  • Preview branches build automatically on Vercel.
  • Production deploys from the production branch used by the app repository.
  • Preview deployments can use PREVIEW_* database variables.
  • Production Salesforce writes must be handled carefully and should not be confused with sandbox preview testing.

Environment model

Feature branch ── deploys to ── Vercel preview
Preview deployment ── should use ── preview database and sandbox-safe settings
Production branch ── deploys to ── production app
Production app ── writes to ── production Salesforce only when intended

Docs deployment model

This docs portal deploys separately from the app at docs.ca-tools.io. That gives documentation updates their own preview URL and production release path.

Docs deployment should stay project-neutral. Adding a new product section, such as PoolTracker / Preseason, should not require a production deploy of that application. Conversely, shipping a production application change should not automatically imply the docs are current unless the relevant documentation change has also been reviewed and deployed.

Release discipline

Docs updates should cite the app version or commit they describe when behavior is version-sensitive. Operational guides should be reviewed after each major workflow change.

Pitfalls

  • Do not test production pricebook writes from a preview deployment unless the change was explicitly approved for production.
  • Do not assume a preview build uses the same database variables as production.
  • Do not update docs for behavior that has not been committed, pushed, and deployed to the relevant environment.
Last updated on
Proposal ToolsRoles and Permissions