docs: specify platform operations

This commit is contained in:
2026-08-20 18:11:01 +03:30
parent 07c61fdd09
commit d651e0c845
2 changed files with 541 additions and 0 deletions

View File

@@ -51,3 +51,23 @@ Applied in the frontend repository's `DESIGN.md`: Persian RTL layout, right-side
Framework decisions remain subordinate to capability requirements. SvelteKit is used as a TypeScript application framework without assuming SEO/SSR; Go is used for the backend with architecture, DI, database access, and API choices approved through the specification process.
## Platform operations documentation
- Docker Compose application model: <https://docs.docker.com/compose/intro/compose-application-model/>
- Docker Compose startup order: <https://docs.docker.com/compose/how-tos/startup-order/>
- Docker Engine logging: <https://docs.docker.com/engine/logging/configure/>
- Docker rootless mode: <https://docs.docker.com/engine/security/rootless/>
- Nginx proxy module: <https://nginx.org/en/docs/http/ngx_http_proxy_module.html>
- Nginx TLS module: <https://nginx.org/en/docs/http/ngx_http_ssl_module.html>
- PostgreSQL backup and restore: <https://www.postgresql.org/docs/current/backup.html>
- PostgreSQL SQL dumps: <https://www.postgresql.org/docs/current/backup-dump.html>
- Gitea Actions overview: <https://docs.gitea.com/usage/actions/overview/>
- Gitea runner: <https://docs.gitea.com/runner/>
Applied in `PLATFORM-OPERATIONS-SPEC.md` through health-gated Compose startup, isolated networks and secrets, bounded container logs, TLS/SSE proxy behavior, logical PostgreSQL backup with guarded restore, and trusted-runner release orchestration. Exact product versions and runner capabilities remain explicit approval decisions rather than assumptions.
## Qlockify deployment reference
Local read-only source: `D:/Programing/Scripts/Qlockify/qlockify-deployment`
Applied as a proven three-repository, Compose, Nginx, ACME, nested-checkout, and encrypted off-host backup reference. ZarinPal deliberately hardens the pattern by deploying immutable image digests instead of resetting/building mutable server checkouts, excluding environment/secrets from database backup packages, separating migrations/import from application startup, guarding production restore, and omitting scheduled application workers.