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

feat: deploy through shared Caddy ingress

Browse Source
This commit is contained in:
Amirhossein Khalili
2026-08-22 21:48:26 +08:00
parent e2decb9e01
commit 64404bb7cf
9 changed files with 473 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -6,6 +6,8 @@
- Depends on: all deployable backend and frontend capability contracts
- Last updated: 2026-08-20
> **2026-08-22 ingress amendment:** ADR 0006 supersedes the dedicated Nginx/Certbot edge described below. The host's existing Caddy deployment owns ports 80/443, TLS, canonical-host routing, security headers, API/SSE proxying, and frontend proxying. This project publishes no ports and attaches only `backend` and `frontend` to the external `caddy_proxy` network. All private-data, manual-release, migration/import, secret, health, backup, and recovery requirements remain in force.
## Confirmed intent
Deploy `zarinpal.amiirkhl.ir` on one Ubuntu server using the proven Qlockify operating model: three nested Git repositories, Docker Compose builds performed on the server, Nginx as the only public entry point, automatic Let's Encrypt TLS, PostgreSQL 18, Redis 7 Alpine, a Go API and event-driven worker, and a static frontend.