Matheus
d66170c795
- users + tenant_memberships tables (tenant-scoped)
- RLS policy on tenant_memberships using set_config('app.current_tenant_id', ...)
- withTenantContext() helper for transaction-scoped tenant context
- separate non-superuser app role (b2bcall_app): the default Docker postgres
user is SUPERUSER and always bypasses RLS even with FORCE, so the app must
never connect through the migration/owner role. Documented in
docs/TENANT_ISOLATION.md.
- automated isolation test proving tenant A never sees tenant B's data
2.3 KiB
2.3 KiB
TODO — B2BCall
PHASE 01 — Infrastructure
- Diagnóstico do servidor (Debian 13, 2 vCPU, ~1.9GB RAM, 26GB disco livre)
- Docker + Docker Compose instalados
- Estrutura de monorepo criada (apps/, packages/, infrastructure/, scripts/, docs/)
- PostgreSQL 18 (docker-compose, porta 127.0.0.1:5432)
- Redis 7 (docker-compose, porta 127.0.0.1:6379)
- Secrets gerados em
.env(POSTGRES_PASSWORD, REDIS_PASSWORD, JWT_SECRET, JWT_REFRESH_SECRET, ENCRYPTION_KEY, ESL_PASSWORD) FREESWITCH_PATconfigurado em.env(não commitado)- FreeSWITCH (build/imagem própria, ver risco de RAM abaixo)
- nginx (reverse proxy)
PHASE 02 — SaaS Core
- Monorepo Node.js/TypeScript (pnpm workspaces, tsconfig base)
- Node 22 LTS + pnpm instalados no host
packages/database(Prisma 7 + driver adapterpg, migration inicial)packages/types(TenantStatus, AgentState),packages/shared- Tabela
tenantscriada via migration (seção 29 do agente.md)
PHASE 03 — Tenant Isolation
- Tabelas
users+tenant_memberships(tenant-scoped) - RLS (
ENABLE/FORCE ROW LEVEL SECURITY+ policy) emtenant_memberships - Tenant context via
set_config('app.current_tenant_id', ..., true)(transaction-local) - Helper
withTenantContext()empackages/database - Role de banco separado para runtime (
b2bcall_app, sem SUPERUSER/BYPASSRLS) — achado crítico: o role padrão do Docker Postgres é SUPERUSER e SEMPRE ignora RLS, até com FORCE. Verdocs/TENANT_ISOLATION.md. - Teste automatizado de isolamento (
pnpm --filter @b2bcall/database run test:isolation)
PHASE 04 — Authentication / RBAC
- Login (Argon2id), access/refresh tokens
- roles/permissions/user_roles/role_permissions
PHASE 05+ — ver agente.md seções 15 em diante (FreeSWITCH, Telefonia, Call Center,
Predictive Dialer, Recordings, AI, Billing, Frontend, Reports, Security, Tests)
Riscos conhecidos
- RAM da VM (1.9GB total): insuficiente para rodar toda a stack (Postgres + Redis + FreeSWITCH + múltiplos workers Node + Next.js) simultaneamente sem swap/OOM. Avaliar upgrade de RAM antes de subir FreeSWITCH + frontend + workers juntos.
- Disco (26GB livre): build do FreeSWITCH + imagens Docker + gravações vão consumir
espaço rápido. Monitorar com
df -h.