DocsGo to Dashboard

Delivery

Deploy acceleration

Configuration changes are never live the moment you save them. They sit in a draft table until you explicitly deploy, at which point they're copied into the configuration the proxy actually reads.

How it works

  • Edits are written to a draft config and the domain is marked deploymentStatus: DRAFT
  • Deploying copies draft to deployed inside a single transaction, so the proxy never sees a half-applied config
  • A tokenized /accelerate/:token URL lets you preview the deployed behavior, including HTML/CSS rewriting, ahead of a full production cutover

Good to know

  • The tokenized preview is a demo path, not the production CDN flow — DNS, CNAME, and managed TLS onboarding are a separate, upcoming step
  • Because deploy is transactional, a failed deploy leaves the previous live config untouched
WebOptiva