Stop syncing static bucket objects (#37)

Author: dnywh

README.md

@@ -150,7 +150,7 @@ Use local Studio, `psql`, or the hosted Supabase dashboard for browsing rows and
 - `npm run supabase:reset` rebuilds the local database schema and data
 - `npm run seed:local-media` uploads local demo media into local Supabase buckets
 
-The demo media under `supabase/storage/avatars`, `supabase/storage/listing_avatars`, and `supabase/storage/listing_photos` is for local development only. Hosted Supabase branches and production should not sync those objects from Git.
+The demo media under `supabase/storage/` is for local development only. Hosted Supabase branches and production should not sync bucket objects from Git.
 
 Keep all local and preview data sanitized. Do not export or commit production data.
 

docs/supabase-local-first.md

@@ -120,11 +120,10 @@ The seed also creates:
 - 1 chat thread
 - 2 chat messages
 - seeded profile avatars and listing photos in local Supabase Storage
-- a sample static bucket object at `static/promo-kit.zip`
 
 The demo data is synthetic and safe to keep in Git.
 
-When `NEXT_PUBLIC_SUPABASE_URL` points at `http://127.0.0.1:54331`, avatar and listing-photo uploads also go to the local Supabase buckets rather than production. The repo-tracked demo media is uploaded only by `npm run seed:local-media`, not by hosted Supabase deploys.
+When `NEXT_PUBLIC_SUPABASE_URL` points at `http://127.0.0.1:54331`, avatar and listing-photo uploads also go to the local Supabase buckets rather than production. Repo-tracked bucket media is uploaded only by `npm run seed:local-media`, not by hosted Supabase deploys.
 
 ## Fresh Computer Setup
 

supabase/config.toml

@@ -105,7 +105,6 @@ allowed_mime_types = ["image/png", "image/jpeg", "image/webp"]
 [storage.buckets.static]
 public = true
 file_size_limit = "50MiB"
-objects_path = "./storage/static"
 
 [auth]
 enabled = true