morteza/TorbatYar
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
d92e1df332
TorbatYar/backend/services/communication
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

Communication Service

Independent Enterprise Communication Platform for TorbatYar SuperApp.

  • Database: communication_db (sole owner)
  • Port: 8005
  • Version: 0.8.10.1
  • Permission prefix: communication.*

Boundaries

This service is shared infrastructure. It does not belong to CRM, Loyalty, Restaurant, or any business module.

Consumers interact only via HTTP APIs and events. No module may call external SMS/email/push providers directly.

Channels

Designed for: SMS, Email, Push, WhatsApp, Telegram, Rubika, Voice, Future.

Initially active: SMS (mock + Payamak adapters).

Docs

See docs/communication-phase-8.md.