Architecture ERP¶

Vue d ensemble¶

L application se deploie via un seul docker-compose dans Coolify. - erp_frontend sert l app React/Vite. - erp_docs sert la doc MkDocs. - Supabase fournit Auth, DB, Storage, Realtime et Edge Functions via Kong.

Diagramme¶

graph TD
  User[Utilisateur] -->|HTTPS| App[ERP Frontend (oben-services.com)]
  User -->|HTTPS| Docs[Documentation (doc.oben-services.com)]
  App -->|HTTPS| Kong[Kong API Gateway (supabase.oben-services.com)]
  Kong --> Auth[Auth (GoTrue)]
  Kong --> Rest[PostgREST API]
  Kong --> Realtime[Realtime]
  Kong --> Storage[Storage API]
  Kong --> Functions[Edge Functions]
  Auth --> DB[(Postgres)]
  Rest --> DB
  Realtime --> DB
  Storage --> DB
  Functions --> DB
  Storage --> Bucket[(Storage Objects)]

Flux principal¶

Le frontend utilise SUPABASE_PUBLIC_URL + ANON_KEY.
Kong route les requetes vers les services Supabase.
Les Edge Functions utilisent la SERVICE_ROLE_KEY cote serveur.
Les donnees sont stockees dans Postgres et Storage.

Composants cles¶

erp_frontend: app utilisateur.
kong: point d entree API.
functions: runtime Edge Functions.
db: base Postgres.
storage: objets photo.
erp_docs: documentation publique.