Skip to main content

FF-71: Supabase Storage Decision

Status: Deferred in Backlog

Decision date: 2026-07-31

Active provider: Supabase Storage

Decision​

FF RESTaurent will continue using Supabase Storage for application media. FF-71, the proposed migration from Supabase Storage to Google Cloud Storage (GCS), is deferred and is not part of an active phase or milestone.

This decision applies only to media storage. The completed GCP platform work remains in place: the web and API run on Cloud Run, PostgreSQL runs on Cloud SQL, and deployment artifacts and runtime secrets use the established GCP foundation.

Active storage contract​

The API remains the only trusted storage client. Browser code must never receive the Supabase service-role key.

PurposeContract
Supabase projectSUPABASE_URL
API credentialSUPABASE_SERVICE_ROLE_KEY
Public restaurant and profile imagesSUPABASE_PUBLIC_BUCKET
Private payment QR imagesSUPABASE_QR_BUCKET
Private URL lifetimeSUPABASE_SIGNED_URL_TTL_SECONDS

Public media is served from the configured public bucket. Payment QR media stays private and is exposed only through short-lived signed URLs generated by the API.

Why FF-71 is deferred​

  • Supabase Storage is already the shipped and validated media provider.
  • Keeping the current provider avoids an object-copy cutover, URL compatibility work, checksum reconciliation, and rollback risk without a demonstrated product need.
  • The existing API-only credential boundary, public/private bucket split, image validation, and signed-URL behavior remain appropriate for the current scale.
  • Moving the application and database to GCP does not require moving media to GCS.

Historical GCS implementation​

The experiment is preserved for future reference:

These references are knowledge artifacts only. They are not approved deployment instructions, and the GCS runtime/configuration changes must not be deployed. PR #60 was repurposed to restore the active Supabase contract and add a regression guard.

Conditions for reconsideration​

Resume FF-71 only after an owner decision based on a concrete operational, availability, cost, compliance, or product requirement. A new implementation plan must include:

  1. A current inventory of all public and private objects.
  2. Snapshot-consistent counts plus object size and checksum verification.
  3. URL compatibility and signed-URL behavior for existing database records.
  4. A staged migration and authenticated application smoke test.
  5. A documented cutover gate and rollback path.
  6. Production approval before any object copy or runtime configuration change.