Free, Open Source, Self-Hosted WhatsApp API Gateway
TypeScript apibotgatewayself-hostedwhatsappwhatsapp-apiwhatsapp-automationwhatsapp-botwhatsapp-gatewaywhatsapp-gateway-apiwhatsapp-webwhatsapp-web-api
docs(scaling): persist all of /app/data in the Swarm example
Yudhi Armyndhariscff29fea63e3
diff --git a/docs/13-horizontal-scaling.md b/docs/13-horizontal-scaling.mdindex 6087e24e5..c9d6e69c7 100644--- a/docs/13-horizontal-scaling.md+++ b/docs/13-horizontal-scaling.md@@ -288,7 +288,9 @@ services:# node, which has to wait out its own previous lease). Defaults to the container hostname.- NODE_ID={{.Node.Hostname}}-{{.Task.Slot}}volumes:- - sessions:/app/data/sessions+ # The whole data tree, not only sessions/: main.sqlite (API keys, audit log), baileys/,+ # media and the generated secrets live there too, and a replaced task would lose them.+ - openwa-data:/app/datanetworks:- openwa-netdepends_on:@@ -329,7 +331,7 @@ services:volumes:postgres-data:redis-data:- sessions:+ openwa-data:networks:openwa-net:@@ -350,7 +352,7 @@ docker service lsdocker service ps openwa_openwa```-> **Do not scale the `openwa` service** (`docker service scale openwa_openwa=N`). The `sessions`+> **Do not scale the `openwa` service** (`docker service scale openwa_openwa=N`). The `openwa-data`> volume above is declared with the default local driver (not `external`), so Swarm creates one per> node: replicas co-located on a single node share that directory and corrupt the WhatsApp auth> state, while replicas placed on other nodes each get a fresh empty volume and start an