chrisfu 80323afd10 Fix Supabase storage class injection: write persistence.*.storageClassName, add synology guard ... Root cause: render_supabase.py wrote to deployment.*.storageClass (ignored by Helm chart PVC templates) instead of persistence.*.storageClassName (_pvc.tpl:43 is the real path). Also deploy.sh --set persistence.* args only ran in k8s mode, and stale values.generated.json was reused across deploys. Together these caused Supabase PVCs to fall through to pi-local-iscsi (pi SD card), crashing the node under memory pressure. - supabase/helm/render_supabase.py: - write persistence.{functions,imgproxy,snippets,storage,deno,minio}.storageClassName using the correct Helm chart path (_pvc.tpl:43) - add synology guard: raise SystemExit if storage class is not synology/merlin/myrddin - remove broken deployment.*.storageClass writes - supabase/deploy.sh: - delete stale values.generated.json before every helm_render_values call - fall back to reading SUPABASE_STORAGE_CLASS from cfg file via python3 if env not set - add bash synology guard: die if storage class is not iSCSI/NFS mounted - extend helm_set_args to include persistence.minio.storageClassName and apply --set persistence.* for ALL modes (not just k8s) Co-authored-by: Junie <junie@jetbrains.com>		2026-03-24 14:39:43 -07:00
..
port-mapping.cfg	Fix port-mapping.cfg: add missing [PortMappings] section header for configparser	2026-03-24 14:28:55 -07:00
prole.cfg	Fix Supabase storage class injection: write persistence.*.storageClassName, add synology guard	2026-03-24 14:39:43 -07:00