docs(docs): V1-2.3 second reviews, worker-verify memory in DEPLOY

This commit is contained in:
bchanot committed 2026-11-01 18:20:38 +01:00
1 parent 6b40a00477
commit 96b19e5a87
2 files changed
+7

No files matched your search

+3
View File
@@ -176,6 +176,9 @@ from the table (STORAGE.md §3.2 lists the optional tuning variables).
The service joins the external network named by `SUPABASE_NETWORK`
(default `supabase_network_faunosteo`, the local CLI stack); it publishes no
port, runs read-only with every capability dropped, 512 MiB, 1 CPU, 64 pids.
The verification service `worker-verify` (V1-2.3) has the same hardening with
1 280 MiB, so its child's 1 GiB address-space limit binds first: a host that
runs it beside the stack needs that memory on top of the 1 GB below.
Browser side, the production CSP `connect-src` must name the Supabase
origin the app talks to (already required since Step 7), and `img-src`
keeps `blob:` (the avatar is shown from a blob URL downloaded under RLS).