2.1 KiB
2.1 KiB
ZarinPal Merchant Analytics — Deployment
This repository is the operational control plane for the hackathon project. It will own Docker Compose, Nginx, environment templates, deployment automation, backup/restore scripts, and cross-repository release orchestration. Product code belongs in the backend and frontend repositories.
Current state: specification and repository bootstrap only. No application or deployment implementation has been approved yet.
Repository topology
zarinpal-analytics-deployment/ # this repository
├── backend/ # ignored checkout of zarinpal-analytics-backend
├── frontend/ # ignored checkout of zarinpal-analytics-frontend
├── docs/
└── (deployment assets only after explicit build authorization)
The intended production hostname is zarinpal.amiirkhl.ir. The deployment shape will follow the proven Qlockify structure while being reviewed and hardened for this service; it is not a byte-for-byte copy.
Documentation workflow
CAPABILITY-MAP.mdis the approved Phase 0 decomposition.- Each capability receives a spec before implementation.
- Surprising or hard-to-reverse decisions receive an ADR in
docs/decisions/. - Raw datasets and database state are never committed.
- Every material change is a small Conventional Commit.
Platform operations documents
docs/PLATFORM-OPERATIONS-SPEC.mddefines the approved manual Qlockify-style production topology, lifecycle, observability phases, security, backup/restore, acceptance, and operator boundaries.docs/QLOCKIFY-ADAPTATION-CONTRACT.mdmaps Qlockify's tracked deployment files and environment layout to the planned ZarinPal artifacts without requiring real server values during planning.docs/runbooks/FIRST-SERVER-BOOTSTRAP.mddefines the safe first-host sequence without implementing a bootstrap script.docs/runbooks/BACKUP-RESTORE.mddefines logical PostgreSQL backup, encryption/retention, guarded restore, and rehearsal.tasks/plan.mdandtasks/todo.mdhold the approval-gated implementation plan. Their presence does not grant implementation authorization.