ComercialRS — Backup Completo

Data: 2026-06-23

Backup por: Hermes

Motivo: Supabase Cloud bloqueado (exceed_egress_quota) — preparando terreno para migração

1. Identificação do Projeto

2. Arquitetura Atual

`

NAVEGADOR USUÁRIO

↓

nginx (comercialrs.rochasalesseguros.com.br)

↓

├── /rest/v1/* → proxy → https://dauftiqcvgaydddoxqhh.supabase.co ⚠️ BLOQUEADO

├── /auth/v1/* → proxy → https://dauftiqcvgaydddoxqhh.supabase.co ⚠️ BLOQUEADO

├── /functions/* → proxy → https://dauftiqcvgaydddoxqhh.supabase.co ⚠️ BLOQUEADO

├── /storage/v1/* → proxy → https://dauftiqcvgaydddoxqhh.supabase.co ⚠️ BLOQUEADO

├── /realtime/* → proxy → https://dauftiqcvgaydddoxqhh.supabase.co ⚠️ BLOQUEADO

└── / (frontend) → arquivos estáticos em /var/www/comercialrs/dist/

META WEBHOOK (porta 8083)

↓

meta_webhook_vps_service.py

↓

Supabase Cloud DB (db.dauftiqcvgaydddoxqhh.supabase.co) ⚠️ BLOQUEADO

TAREFAS AUTOMÁTICAS

↓

task_alerts.py (cron)

↓

Supabase Cloud DB (db.dauftiqcvgaydddoxqhh.supabase.co) ⚠️ BLOQUEADO

`

3. Credenciais — Supabase Cloud (dauftiqcvgaydddoxqhh)

3.1 — Configuração do Projeto

3.2 — .env do ComercialRS (VPS)

Arquivo: /var/www/comercialrs/.env

`

SUPABASE_URL="https://dauftiqcvgaydddoxqhh.supabase.co"

SUPABASE_PUBLISHABLE_KEY="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6ImRhdWZ0aXFjdmdheWRkZG94cWhoIiwicm9sZSI6ImFub24iLCJpYXQiOjE3NzI0NTEzODUsImV4cCI6MjA4ODAyNzM4NX0.OtwMAcrs2L3iH60ppShVTrOuQYSolIwITUPVf1ckswk"

VITE_SUPABASE_PROJECT_ID="dauftiqcvgaydddoxqhh"

VITE_SUPABASE_PUBLISHABLE_KEY="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6ImRhdWZ0aXFjdmdheWRkZG94cWhoIiwicm9sZSI6ImFub24iLCJpYXQiOjE3NzI0NTEzODUsImV4cCI6MjA4ODAyNzM4NX0.OtwMAcrs2L3iH60ppShVTrOuQYSolIwITUPVf1ckswk"

VITE_SUPABASE_URL="https://dauftiqcvgaydddoxqhh.supabase.co"

`

⚠️ ESSAS KEYS SÃO DO CLOUD — ESTÃO BLOQUEADAS

3.3 — Postgres DB (Cloud)

Usado por: meta_webhook_vps_service.py e task_alerts.py

4. Credenciais — Supabase Self-Hosted (VPS)

Docker compose: /docker/deploy-vps/docker-compose.yml

Ambiente: /docker/deploy-vps/.env

4.1 — Postgres Local

4.2 — Anon Key Local (Self-Hosted)

`

eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6InJvY2hhc2FsZXMiLCJyb2xlIjoiYW5vbiIsImlhdCI6MTc4MjE0MDAxMiwiZXhwIjoxODEzNjc2MDEyfQ.zSTyXFB2i9xsPJQ0rTCEhEL0JnMTj0brfExdqa85VWU

`

✅ FUNCIONA no localhost:8000

4.3 — JWT Secrets

4.4 — Containers Ativos

4.5 — Tabelas no DB Local (Self-Hosted)

`

broker_links

cms_content

custom_roles

leads

profiles (5 linhas — dados genéricos, NÃO são dados do ComercialRS)

tool_role_access

user_roles

user_profiles

`

⚠️ O DB LOCAL NÃO TEM OS DADOS DO COMERCIALRS — está vazio

5. Nginx

Arquivo: /etc/nginx/sites-enabled/comercialrs.rochasalesseguros.com.br

`

server_name: comercialrs.rochasalesseguros.com.br

root: /var/www/comercialrs/dist

ssl: letsencrypt (fullchain.pem + privkey.pem)

location /rest/v1/* → proxy → https://dauftiqcvgaydddoxqhh.supabase.co (apikey embedada)

location /auth/v1/* → proxy → https://dauftiqcvgaydddoxqhh.supabase.co (apikey embedada)

location /functions/v1/* → proxy → https://dauftiqcvgaydddoxqhh.supabase.co (apikey embedada)

location /storage/v1/* → proxy → https://dauftiqcvgaydddoxqhh.supabase.co (apikey embedada)

location /realtime/v1/* → proxy → https://dauftiqcvgaydddoxqhh.supabase.co (apikey embedada)

location / → try_files $uri $uri/ /index.html

APikey embedded no proxy (CLOUD):

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6ImRhdWZ0aXFjdmdheWRkZG94cWhoIiwicm9sZSI6ImFub24iLCJpYXQiOjE3NzI0NTEzODUsImV4cCI6MjA4ODAyNzM4NX0.OtwMAcrs2L3iH60ppShVTrOuQYSolIwITUPVf1ckswk

`

6. Meta WhatsApp Business API

6.1 — Webhook Server

6.2 — Credentials (armazenadas na tabela automations_config do Cloud)

Retornadas pela query:

`sql

SELECT meta_access_token, meta_phone_number_id FROM public.automations_config LIMIT 1

`

⚠️ Estão no DB Cloud (bloqueado)

6.3 — Fluxo

1. Meta envia webhook → /meta-webhook → meta_webhook_vps_service.py

2. Script conecta no DB Cloud db.dauftiqcvgaydddoxqhh.supabase.co (bloqueado)

3. Atualiza tasks e meeting_status

6.4 — Status Keywords

• - in_progress: iniciada, começou, andamento, start, started
• - completed: concluída, finalizada, done, fechada
• - remarketing: remarketing, remar, rmk, remercar

6.5 — Botões

Formato payload: status|TASK_ID (ex: in_progress|abc123...)

---

7. Edge Functions (Supabase Cloud)

7.1 — Lista Completa de Funções

`

admin-reset-user-password — Reset senha via admin

admin-update-user-email — Update email via admin

crm-lead-sync — Sync leads CRM externo

crm-mirror-health — Health check do CRM mirror

crm-sales-pipeline — Pipeline de vendas

crm-sales-sync — Sync de vendas

db-check-tables — Check tablas

db-inspect — Inspect database

dispatch-automation — Dispatch automação WhatsApp

firecrawl-extract-meeting — Extrair meeting

init-whatsapp-table — Inicializar WhatsApp table

inspect-db-profiles — Inspect profiles

resend-pending-meetings — Reenviar meetings pendentes

send-reminders — Enviar lembretes

sync-all-tasks — Sync todas tasks

sync-painel-to-chatwoot — Sync Painel → Chatwoot

sync-profiles — Sync profiles

test-network — Test network

uazapi-status-webhook — UAZAPI status webhook

update-responsibles — Update responsibles

update-profile-user-id — Update profile user_id

create-broker-links — Criar broker links

chatwoot-webhook — Webhook Chatwoot

meta-webhook — Webhook Meta

test-webhook — Test webhook

`

7.2 — Função Principal (Self-Hosted)

7.3 — Funções do Cloud Ausentes no Self-Hosted

8. Tabelas do ComercialRS (Supabase Cloud)

Tabela: profiles

`sql

id uuid (PK, = auth.users.id)

user_id uuid (FK → auth.users.id)

full_name text

email text

role text

onboarding_done boolean

`

Tabela: tasks

`sql

id uuid PK

created_by uuid FK → profiles.id

responsible_id uuid FK → team_members.id

title text

status text (todo, in_progress, completed, remarketing)

due_date timestamptz

`

Tabela: team_members

`sql

id uuid PK (DIFERENTE de profiles.id)

profile_id uuid FK → profiles.id

name text

phone text

role text

`

Tabela: meetings

`sql

id uuid PK

responsible_id uuid FK → team_members.id

title text

start_date timestamptz

status text

meeting_status text

created_by uuid

`

Tabela: automations

`sql

id uuid PK

key text UNIQUE

name text

description text

icon text

status boolean

last_run_at timestamptz

`

Tabela: automations_config

Singleton global (user_id IS NULL). Campos:

Tabela: message_log

meta_message_id, task_id, responsible_id, phone, status

Tabela: incoming_messages

Respostas recebidas via webhook Meta

Tabela: alert_throttle

Anti-spam (janela 30min): signature, event_type, target_phone, responsible_id, task_ids, expires_at

Tabela: crm_leads

Espelho do CRM externo (sincronizado por n8n/cron)

Tabela: broker_links

(?) Usado para links de corretores

9. Automations (Edge Functions Cron)

10. Scripts Python (VPS)

10.1 — task_alerts.py

10.2 — run_task_alerts.sh

11. Build e Deploy

`bash

Build

cd /var/www/comercialrs

nvm use 20

npm run build

Output: /var/www/comercialrs/dist/

Deploy (manual)

cp -r /var/www/comercialrs/dist/* /var/www/comercialrs/dist_new/ 2>/dev/null || true

`

12. Domínios e SSL

SSL path: /etc/letsencrypt/live/comercialrs.rochasalesseguros.com.br/

13. Plano de Migração para Self-Hosted (definitivo)

Passo 1: Desbloquear Cloud (remover spend cap)

Passo 2: Exportar dados do Cloud

`bash

Exportar todas as tabelas (quando Cloud estiver acessível)

via pg_dump ou scripts Python

`

Passo 3: Preparar Self-Hosted

Passo 4: Migrar Edge Functions

Passo 5: Trocar .env do ComercialRS

`

SUPABASE_URL="http://localhost:8000" (ou URL do Kong local)

SUPABASE_PUBLISHABLE_KEY=""

`

Passo 6: Atualizar nginx

Passo 7: Testar tudo

Rollback

14. Contatos e Acessos

Supabase Cloud Dashboard

VPS

15. Histórico de Problemas Resolvidos

16. Arquivos Importantes

Documento criado em 2026-06-23 por Hermes — atualizado automaticamente