morteza/TorbatYar
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
d579d0b142
TorbatYar/backend/services/sports_center
History
Mortezakoohjani e41ecfad4c Sync platform docs, infra, and module services with Accounting integration. 
Include Loyalty/Communication/Sports Center backends and registry updates alongside production nginx and compose wiring.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-25 22:35:23 +03:30
..
alembic Sync platform docs, infra, and module services with Accounting integration. 2026-07-25 22:35:23 +03:30
app Sync platform docs, infra, and module services with Accounting integration. 2026-07-25 22:35:23 +03:30
scripts Sync platform docs, infra, and module services with Accounting integration. 2026-07-25 22:35:23 +03:30
alembic.ini Sync platform docs, infra, and module services with Accounting integration. 2026-07-25 22:35:23 +03:30
Dockerfile.dev Sync platform docs, infra, and module services with Accounting integration. 2026-07-25 22:35:23 +03:30
pytest.ini Sync platform docs, infra, and module services with Accounting integration. 2026-07-25 22:35:23 +03:30
README.md Sync platform docs, infra, and module services with Accounting integration. 2026-07-25 22:35:23 +03:30
requirements.txt Sync platform docs, infra, and module services with Accounting integration. 2026-07-25 22:35:23 +03:30

README.md

Sports Center Platform Service

Independent enterprise microservice for generic sports center operations.

  • Phase: 9.2 Member Management
  • Version: 0.9.2.0
  • Database: sports_center_db (sole owner)
  • API port: 8006
  • Permission prefix: sports_center.*
  • ADR: ADR-014

Ownership

Sports Center owns only sports business aggregates (centers, branches, sports catalog, membership catalog, members, membership assignment, cards/waivers/documents, coaches shell, facilities, devices, connector contracts, configuration, audit).

It must not own Accounting, CRM, Loyalty, Communication, Notification, Storage, Identity, AI, Automation, or Customer360 — consume those via API + Events only.

Architecture

  • Database-per-service (ADR-001)
  • Row-level multi-tenancy via tenant_id (ADR-003)
  • Adapter-based connector framework (no vendor logic in business services)
  • Generic sport model — no sport-specific business rules hardcoded

Docs