mirror of
https://github.com/dartdavros/chatballs.git
synced 2026-10-14 13:19:01 +03:00
Andrey
549d1faada
Single idempotent write boundary provision_organization coordinates Organization, OWNER membership or invitation, subscription/usage, system departments sales/support, audit and transactional outbox in one transaction under set_local_tenant. - New hub_platform.platform domain: PlatformOperator, hash-only PlatformToken, OrganizationProvisioning process record with state machine PENDING/IN_PROGRESS/WAITING_FOR_OWNER/COMPLETED/FAILED. - Platform API POST platform.custocrm.ru/api/v1/organizations: machine token auth + capability platform.organizations.provision, Idempotency-Key header, replay/conflict handling, no secrets in response. - OWNER invitation accept (accept_invitation + auth view) activates organization, subscription and first usage period; idempotent re-accept does not duplicate membership or period. - DB write boundary (tenancy/0005): platform INSERT/UPDATE on identity_organization and platform DML + tenant-isolation policy on identity_department/identity_employeeprofile; Organization.status ACTIVE/PENDING_OWNER (identity/0015). - System department codes centralised in identity/system_departments. Machine token without MFA is an owner-approved deviation from ADR-HUB-0031 section 9; human+MFA platform login belongs to track D. concurrent_p2p_calls derived from membership count is a separate C07 decision (PLAN-CUSTOCRM-0003 section 12). Gate: idempotent replay creates no second tenant; operator never becomes OWNER; provisioning creates no AI-agent/product/connection/demo data. Full backend regression 379 passed (one pre-existing unrelated SOCKS5 test); 19 C06 targeted tests passed. UI unchanged. Production migration/deploy, publication of production PlanVersion and bootstrap of the production platform token are not part of this commit.
CustoCRM
Canonical implementation workspace for hub.edevs.tech.
Local start
Copy-Item .env.example .env
.\scripts\start.ps1
The local compose stack contains:
- isolated app, platform, and loopback-only admin Django runtimes;
- background worker;
- PostgreSQL;
- Redis;
- Internal Hub UI;
- Web Chat UI;
- local Nginx reverse proxy.
No production secrets are stored in the repository.
Default local URLs:
- App gateway:
http://app.localhost/ - Platform health:
http://platform.localhost/api/v1/health/live/ - Django admin (loopback only):
http://127.0.0.1:18001/admin/ - Internal Hub UI (direct Vite):
http://localhost:5173 - Web Chat:
http://localhost:5175 - App API (direct):
http://localhost:8010/api/v1
Local accounts (TOTP disabled). These credentials are fixed — do not change them:
- OWNER —
owner@edevs.tech/Owner-Local-2026 - OPERATOR —
a.kotova@edevs.tech/Operator-Local-2026
Bootstrap the organization and both accounts:
docker compose run --rm backend-app python manage.py bootstrap_owner --email owner@edevs.tech --password Owner-Local-2026 --name "Иван Петров"
Tests
All suites run in Docker, so no manual environment is required — the test runners auto-detect themselves and relax production hardening (secret-key fail-fast, SSL redirect, throttling) for the duration of the run.
Run everything (backend tests, frontend unit tests, typechecks):
.\scripts\check.ps1
Individual suites:
# Backend (pytest + pytest-django)
docker compose run --rm backend-app pytest
# Frontend unit tests (vitest)
docker compose run --rm frontend npm run test
# End-to-end (Playwright, internal-ui) — auto-starts the dev server
npx playwright install chromium # one-time
npx playwright test --project=internal-ui
Backend pytest configuration lives in apps/backend/pytest.ini (it must sit
next to manage.py so it is also visible inside the backend container).