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

docs: define bootstrap and schema proposal

Browse Source
This commit is contained in:
Amirhossein Khalili
2026-08-20 13:47:22 +03:30
parent b14807e480
commit 5e83da4a19
4 changed files with 94 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@@ -12,7 +12,7 @@ Place the provided archive at:
data/incoming/challenge_data.csv.gz
```
The entire `data/incoming/` payload is ignored by Git. Future import tooling will read from this location (or an explicitly supplied path), stream the compressed CSV, validate it, and write a tracked import manifest containing the source checksum, schema version, row counts, quality results, and importer revision. The raw file and resulting PostgreSQL data are not committed.
The entire `data/incoming/` payload is ignored by Git. The one-time bootstrap importer will read from this location (or an explicitly supplied path), stream the compressed CSV, validate it, and write an import manifest containing the source checksum, schema version, row counts, quality results, and importer revision. It is an administrative backfill/recovery command, not a scheduled ingestion job. Future production payment data is populated in PostgreSQL by ZarinPal through an upstream contract outside this project's scope. The raw file and resulting PostgreSQL data are not committed.
## Planned runnable boundaries
@@ -24,4 +24,3 @@ One repository may expose several small `cmd/` entry points while sharing domain
- analytics refresh/background job, only if the approved spec requires one
The exact package layout is deferred until the Go architecture and DI decisions are approved.