How apptesters-org/apptesters_repo works
File structure
• Top-level:
• .github/workflows/schedule.yml – CI/CD scheduler (runs daily)
• generate_json.py, get_bundle_id.py – ETL scripts that pull or process app data
• Data artifacts: apps.json, bundleId.csv, plus raw CSV backups and JSON under genres/
• Pattern: a lightweight ETL → static-site pipeline, hosted via GitHub Pages or similar.
Extract README insights
• Describes daily-updated IPA library, lifetime signing certificates, no back-end server, no database—pure static.
• Workflow automates JSON regeneration and site deployment.
a. Main components
1. External Data Sources (e.g., App Store APIs, proprietary scraping endpoints)
2. CI/CD Scheduler (GitHub Actions schedule.yml)
3. ETL Layer
• get_bundle_id.py
• generate_json.py
4. Data Artifacts
• bundleId.csv
• apps.json
• genres/*.json
5. Static Website
• CNAME for domain mapping
6. Hosting & CDN (GitHub Pages or equivalent)
7. End Users (Web Browsers, Mobile Browsers)
b. Relationships & interactions
• CI Scheduler → triggers ETL scripts
• ETL scripts ↔ External Data Sources (pull fresh IPA metadata)
• ETL scripts → generate Data Artifacts (JSON/CSV)
• Commit & push Artifacts + website files → Hosting platform (GitHub Pages)
• Users → HTTP GET to CDN → receive index.html & fetch apps.json → render UI
c. Architectural patterns & design principles
• “Pipeline as code”: CI/CD defines a scheduled ETL pipeline
• Static-only front end: no server processes at runtime
• Data-first separation: JSON/CSV as source of truth, decoupled from presentation
• Incremental updates: schedule runs produce daily snapshots
d. Key technologies & frameworks
• GitHub Actions (CI/CD)
• Python 3.x for ETL scripts
• JSON/CSV for data interchange
• GitHub Pages (or static-site host) + CNAME for custom domain
• Optional: any JS/CSS libs referenced in index.html (e.g., Vue/React or vanilla)