starcoach-hackathon/zarinpal-analytics-deployment
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify production data ownership

Browse Source
This commit is contained in:
Amirhossein Khalili
2026-08-20 13:47:30 +03:30
parent b5728285f4
commit cf68517b3a
2 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
AGENTS.md
View File

@@ -28,9 +28,9 @@ This repository owns deployment concerns only. Backend and frontend directories
## Operational baseline
- Everything runs through Docker, Docker Compose, Bash scripts, and environment files/templates.
- The CSV-to-PostgreSQL workflow is a one-time administrative bootstrap/recovery command, never a scheduled ingestion service. ZarinPal owns future production payment writes.
- Nginx is the only public entry point. PostgreSQL and internal services are not internet-exposed.
- Health checks distinguish liveness from readiness.
- Backups are encrypted where supported, validated, retention-aware, and paired with rehearsed restores.
- Restore operations must validate the exact destination and require an explicit production confirmation guard.
- CI/CD deploys immutable revisions, runs pre/post-deploy checks, and has a documented rollback.