Deployment Overview¶
Summary¶
Use this page to choose a deployment strategy, run the right guide, and validate release readiness.
Outcome¶
After using this guide, you should be able to select the right deployment path, complete the required preflight checks, and verify that the deployment is healthy enough for normal editing and publishing use.
Choose your path¶
| Deployment path | Best fit | Primary tradeoff |
|---|---|---|
| Deploy to Azure | Azure-native operations and managed services | More cloud-service configuration up front |
| Deploy with Docker | Container workflows and local parity | You manage runtime orchestration and updates |
| Deploy to Cloudflare Edge | Edge-heavy delivery and global caching | More CDN integration complexity |
| Run Demo Deployment | Evaluation, demos, and onboarding | Not intended as a production baseline |
Deployment phases¶
flowchart TD
Plan[Select deployment path] --> Preflight[Validate prerequisites and secrets]
Preflight --> Deploy[Run target deployment guide]
Deploy --> Verify[Run health and publish checks]
Verify --> Operate[Enable CI/CD, monitoring, rollback]
Preflight checklist¶
- Confirm infrastructure access and deployment credentials.
- Validate required runtime settings for database and storage.
- Confirm Editor and Publisher target URLs.
- Confirm chosen publishing model for your environment topology.
Post-deploy verification¶
A deployment is complete when all of the following pass:
- health endpoint responds successfully,
- editor login and core edit/publish flow works,
- published output is reachable on intended public URLs,
- storage and CDN behaviors match expected cache/update patterns.
Verification¶
This guide is working when you can choose a deployment path confidently, complete the preflight checklist, and confirm a healthy edit-to-publish flow after rollout.
Ongoing operations baseline¶
After first successful deployment, implement:
- release gates in CI/CD,
- rollback playbook with tested recovery steps,
- alerting and service health visibility.
Troubleshooting entry points¶
- Publishing Workflow for promotion and approval issues.
- CI/CD Pipelines for automation failures.
- Troubleshooting for cross-layer diagnostics.