docs: resolve font deployment decision
This commit is contained in:
@@ -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/>
|
||||
|
||||
Reference in New Issue
Block a user