Add Production Deployment & Zero-Downtime Releases section to README
CI / check (push) Failing after 26s
CI / tests-unit (push) Skipped
CI / tests-integration (push) Skipped
CI / tests-ui (push) Skipped
CI / tests-imaging-browsers (push) Skipped
CI / tests-quality (push) Skipped
CI / preflight (push) Skipped
CI / deploy (push) Skipped

This commit is contained in:
openhands committed 2026-10-23 20:13:35 +02:00
1 parent 2ae8127476
commit 201296e837
1 file changed
+16 -1
+16 -1
View File
@@ -1420,7 +1420,22 @@ EpicNext-CMS maintains strict engineering standards enforced through automated t
---
## License
## Production Deployment & Zero-Downtime Releases
EpicNext-CMS is engineered for enterprise-grade production environments with zero-downtime deployment capabilities:
1. **Blue/Green Slot Deployments**:
- Updates run through containerized slot orchestration (`scripts/docker-update.sh`), ensuring seamless transitions between release versions without dropping requests.
- Automatic health check verification (`/api/health`) validates database connectivity, Redis/Valkey status, and RCON liveness before routing production traffic.
2. **Automated Rollback Protection**:
- If a post-cutover health check or startup sequence fails, the system automatically triggers a rollback to the previous stable container image and logs the incident.
3. **High-Performance Caching & Rate Limiting**:
- Integrates with Redis / Valkey for distributed session storage, global rate limiting, and ephemeral response caching.
- Multi-tier anti-DDoS proxy filtering defends against volumetric application-layer abuse with automatic Cloudflare edge-block mirroring.
---
CC BY-NC-SA 4.0. See `LICENSE` for details.
test line