vibecarbon 0.1.5 → 0.1.7

package/carbon/docker-compose.prod.yml

@@ -187,12 +187,22 @@ services:
   # (Internal services still connect directly for better performance)
 
   # ===========================================
-  # EDGE FUNCTIONS (Production)
+  # EDGE FUNCTIONS (Production) — opt-in
   # ===========================================
+  # Off by default: the template ships no real edge functions (only the 404
+  # stub at functions/main/index.ts), so running this container buys nothing
+  # and just adds an idle process. This `profiles:` gate keeps it from starting
+  # on a normal deploy — matching the k8s setup, where functions are likewise
+  # off until needed (deployment.functions.enabled in k8s/values/supabase.values.yaml).
+  # A project that adds a real function opts in with:
+  #   docker compose --profile functions ... up
+  # The functions/ dir is already bundled to the server (see bundle.js), so
+  # enabling the profile works out of the box.
 
   edge-functions:
     image: supabase/edge-runtime:v1.71.2
     container_name: ${PROJECT_NAME}-functions
+    profiles: ["functions"]
     restart: unless-stopped
     security_opt:
       - no-new-privileges:true

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vibecarbon",
-  "version": "0.1.5",
+  "version": "0.1.7",
   "description": "Create and manage production-ready Vibecarbon applications",
   "type": "module",
   "bin": "./src/cli.js",

package/src/lib/deploy/k8s/ha/index.js

@@ -844,6 +844,24 @@ export async function setupReplication(options) {
     ),
   );
 
+  // Mirror of reloadPostgrest() in the base k8s path. The rollout-restart of
+  // supabase-supabase-rest above already refreshes its schema cache, but issue
+  // the canonical NOTIFY explicitly so the app tables stay visible to PostgREST
+  // even if that restart list ever changes — same PGRST205 class the base
+  // deploy guards against. Best-effort (ignoreError): a missed reload
+  // self-heals on the next rest restart.
+  await perfAsync('deploy.ha.replication.reloadPostgrest', () =>
+    runCommandAsync(
+      [
+        'ssh',
+        ...sshOpts,
+        `root@${primaryIp}`,
+        `kubectl exec -i -n vibecarbon supabase-supabase-db-0 -- psql -U supabase_admin -d postgres -c "NOTIFY pgrst, 'reload schema'"`,
+      ],
+      { silent: true, ignoreError: true },
+    ),
+  );
+
   // 4. Initialize standby as a streaming replica of the primary.
   // Modeled after standby-init.sh — runs pg_basebackup directly inside the standby pod
   // connecting to the primary's supabase node via hostPort 5432 (the Hetzner Cloud firewall

package/src/lib/deploy/k8s/k3s.js

@@ -1525,6 +1525,52 @@ export async function applyMigrations({ kubeconfig, projectDir }) {
   }
 }
 
+/**
+ * Reload PostgREST's schema cache after applyMigrations.
+ *
+ * The chart's `rest` (supabase-supabase-rest) pod comes up during helm
+ * `--wait`, BEFORE applyMigrations runs — so its in-memory schema cache
+ * predates the app tables. Reads of /rest/v1/<table> then 404 with PGRST205
+ * ("Could not find the table ... in the schema cache") until PostgREST
+ * reloads. No DDL-watch event trigger exists in the app migrations or db init
+ * to auto-NOTIFY (verified), so issue the canonical reload explicitly.
+ *
+ * This is the k8s mirror of the compose fix (compose/index.js): same intent —
+ * `NOTIFY pgrst, 'reload schema'` on the db — via `kubectl exec` instead of
+ * `docker compose exec`. Best-effort: a missed reload self-heals whenever the
+ * rest pod next restarts (e.g. the k8s-ha replication path rollout-restarts it
+ * anyway), so a failure here is logged, not fatal.
+ *
+ * @param {{kubeconfig: string}} args
+ */
+export async function reloadPostgrest({ kubeconfig }) {
+  const env = { ...process.env, KUBECONFIG: kubeconfig };
+  const { status, stderr } = await execKubectlOnce(
+    [
+      '-n',
+      'vibecarbon',
+      'exec',
+      '-i',
+      '--request-timeout=15s',
+      'supabase-supabase-db-0',
+      '--',
+      'psql',
+      '-U',
+      'supabase_admin',
+      '-d',
+      'postgres',
+      '-c',
+      "NOTIFY pgrst, 'reload schema'",
+    ],
+    { env, killAfterMs: 20_000 },
+  );
+  if (status !== 0) {
+    console.log(
+      `[migrate] PostgREST schema reload NOTIFY failed (non-fatal, self-heals on rest restart): ${(stderr || '').trim().slice(-200)}`,
+    );
+  }
+}
+
 /**
  * Apply cert-manager + vibecarbon-secrets + the project's k8s/infra +
  * k8s/base kustomizations, install supabase via helm, patch the app
@@ -2133,6 +2179,13 @@ export async function applyK3sManifests({
   await perfAsync(`deploy.${perfPrefix}.applyMigrations`, async () =>
     applyMigrations({ kubeconfig, projectDir }),
   );
+  // 8b. Reload PostgREST's schema cache so it sees the tables applyMigrations
+  //     just created. rest came up during helm --wait (before migrations) and
+  //     no DDL-watch trigger exists to auto-NOTIFY — without this, /rest/v1/*
+  //     404s with PGRST205 until rest restarts. Mirrors the compose fix.
+  await perfAsync(`deploy.${perfPrefix}.reloadPostgrest`, async () =>
+    reloadPostgrest({ kubeconfig }),
+  );
   // 9. Wait for app rollout. The deployment template already has
   //    imagePullPolicy: IfNotPresent, so kubelet uses the sideloaded image
   //    without pulling. 300s wasn't enough on a cold deploy where the app