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

docs: adopt manual server deployment

Browse Source
This commit is contained in:
Amirhossein Khalili
2026-08-20 18:35:16 +03:30
parent c16834b153
commit 892d79b6c3
9 changed files with 461 additions and 464 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/decisions/0001-repository-topology.md
View File

@@ -15,6 +15,5 @@ Use three Git repositories: deployment, Go backend, and SvelteKit frontend. The
- Service changes can run focused CI and then trigger the deployment workflow.
- Deployment remains the authoritative location for Compose, Nginx, backup/restore, and server automation.
- A release manifest must record the exact commit SHA of each service; local nested checkouts alone are not sufficient provenance.
- A server-side release record must capture the exact deployment, backend, and frontend commit SHAs before each build; local nested checkouts alone are not sufficient provenance.
- Cross-repository contract changes require coordinated, backward-compatible rollout or an explicit release plan.