mirror of
https://github.com/garrytan/gstack.git
synced 2026-11-22 16:11:34 +01:00
The telemetry backend now takes writes only through its validated endpoint, signed-in Supabase users can read or write nothing, and gstack's tests can no longer send telemetry to the live project. Why: a signed-in prober read two views on 2026-11-19, probes wrote about 2,000 junk rows through the open insert policy, and 41% of all skill-run rows were test-suite traffic. Nothing changes for users until the migrations and edge functions are deployed; the deploy order is under Deploy. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> Review-Finding: p1/red-team#1 reader=red-team Review-Finding: supabase/migrations/008_close_anon_writes.sql:9:published-number reader=core Review-Finding: p2/outside-voice#3 reader=outside-voice
17 lines
770 B
Bash
17 lines
770 B
Bash
#!/usr/bin/env bash
|
|
# Supabase project config for gstack telemetry
|
|
# These are PUBLIC keys — safe to commit (like Firebase public config).
|
|
# RLS denies all access to the anon key. All reads and writes go through
|
|
# edge functions (which use SUPABASE_SERVICE_ROLE_KEY server-side).
|
|
|
|
GSTACK_SUPABASE_URL="https://frugpmstpnojnhfyimgv.supabase.co"
|
|
GSTACK_SUPABASE_ANON_KEY="sb_publishable_tR4i6cyMIrYTE3s6OyHGHw_ppx2p6WK"
|
|
|
|
# Tests must never reach the live project (old test runs left about 554,000
|
|
# fixture rows in it). test-setup.ts sets this for every `bun test`; with it
|
|
# set, a client that falls back to this file finds no endpoint and sends nothing.
|
|
if [ -n "${GSTACK_TEST_BLOCK_LIVE_TELEMETRY:-}" ]; then
|
|
GSTACK_SUPABASE_URL=""
|
|
GSTACK_SUPABASE_ANON_KEY=""
|
|
fi
|