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

docs: resolve font deployment decision

Browse Source
This commit is contained in:
Amirhossein Khalili
2026-08-20 18:13:01 +03:30
parent 0528fb0a8d
commit c16834b153
2 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/PLATFORM-OPERATIONS-SPEC.md
View File

@@ -504,8 +504,6 @@ Exact script names and flags are implementation decisions constrained by the ope
7. Choose the encrypted backup format/key-management mechanism and production restore database-switch strategy.
8. Decide whether certificate renewal runs as a Compose service or a host systemd timer; both must preserve Nginx reload and private-key permissions.
9. Confirm whether one human production approval is available in the forge and who owns deploy, backup, restore, and incident roles during the hackathon.
10. Confirm the licensed font terms permit the approved direct frontend-repository tracking and built-image distribution for `zarinpal.amiirkhl.ir`; application of that approved repository change remains frontend-owned and outside this task.
## References
- Docker Compose application model: <https://docs.docker.com/compose/intro/compose-application-model/>

2
tasks/todo.md
View File

@@ -10,7 +10,7 @@
**Acceptance criteria:**
- [ ] `PLATFORM-OPERATIONS-SPEC.md` status is explicitly approved by the stakeholder.
- [ ] ADR 0002 is accepted or replaced; ADR 0003 remains consistent with frontend commit `64f5ac2`.
- [ ] All ten remaining decisions have named answers/evidence.
- [ ] All remaining platform decisions have named answers/evidence; the frontend font ownership/delivery decision is already resolved by `64f5ac2` and ADR 0003.
**Verification:** Manual stakeholder approval and clean documentation diff.