mirror of
https://github.com/supabase/supabase.git
synced 2026-10-15 14:19:11 +03:00
Alaister YoungandAlaister Young
cb34acd45c
The docs build had a fragile implicit dependency on www's filesystem (`../../../apps/www/public/llms`), flagged by the docs team in #44670. Rather than formalising that dependency with a shared package, this PR eliminates it entirely by making www the sole owner of llms content assembly. **How it works now:** `/llms/[slug]` handles all `/llms/*.txt` requests via a 3-step cascade: 1. Dynamic content — `pricing.txt` generated at request time from `shared-data` imports 2. Local file — product overviews read from `data/llms/` 3. Docs proxy — reference docs (guides, js, dart, etc.) fetched from the docs app No hardcoded slug lists, so adding new content just works. **What changed:** - `apps/docs/scripts/llms.ts` trimmed to only generate per-source reference files — www now owns `llms.txt`, `llms-full.txt`, and product overviews - Removed `generateLlmsPricing.mjs` build script — pricing generated dynamically from `shared-data` - Removed llms rewrites from `rewrites.js` — routes handle everything with consistent `Cache-Control: public, s-maxage=3600, stale-while-revalidate=86400` - Product overview `.txt` files moved from `public/llms/` → `data/llms/` so all requests go through routes for consistent caching **Docs team concerns from GROWTH-773:** | Concern | Resolution | |---------|-----------| | Docs build depends on www files at a fragile relative path | Path removed — docs no longer reads from www | | www restructuring breaks docs with no obvious connection | Eliminated — no cross-app filesystem dependency | | No build order enforcement between www and docs | Not needed — docs doesn't depend on www's build output | ## To test - `curl <preview>/llms.txt` — markdown index with doc + product overview links - `curl <preview>/llms-full.txt` — combined product overviews + docs content - `curl <preview>/llms/pricing.txt` — dynamically generated pricing tables - `curl <preview>/llms/auth.txt` — product overview from local file - `curl <preview>/llms/guides.txt` — proxied from docs app - `curl <preview>/llms/nonexistent.txt` — 404 - Verify `Cache-Control` header on all responses --------- Co-authored-by: Alaister Young <10985857+alaister@users.noreply.github.com>
35 lines
2.3 KiB
Plaintext
35 lines
2.3 KiB
Plaintext
# Supabase Database
|
|
|
|
> Every Supabase project is a dedicated Postgres database, trusted by millions of developers.
|
|
|
|
Supabase Database gives you a full Postgres database with no compromises. It is not a Postgres-compatible alternative or a shared cluster: every project gets its own dedicated Postgres instance that you can connect to directly with any Postgres client.
|
|
|
|
## Key Features
|
|
|
|
- **Dedicated Postgres**: each project is an isolated Postgres instance, not a shared tenant
|
|
- **100% portable**: bring your own Postgres database, or export and migrate away at any time
|
|
- **Auto-generated APIs**: REST (PostgREST) and GraphQL (pg_graphql) APIs generated from your schema, no backend code needed
|
|
- **Table Editor**: spreadsheet-like UI for viewing and editing data, with support for relationships, JSON columns, and foreign key lookups
|
|
- **SQL Editor**: write and save SQL queries directly in the dashboard, with autocomplete and syntax highlighting
|
|
- **Row Level Security**: fine-grained access control using Postgres RLS policies, integrated with Supabase Auth JWTs
|
|
- **40+ extensions**: enable Postgres extensions with a single click (pgvector, PostGIS, pg_cron, pg_stat_statements, and more)
|
|
- **Database Branching**: create isolated database branches synced with git branches, with Vercel Preview support
|
|
- **Read Replicas**: distribute read traffic across replicas in multiple regions for lower latency and higher throughput
|
|
- **Realtime**: subscribe to INSERT, UPDATE, DELETE, and other changes via WebSockets
|
|
- **Database Webhooks**: trigger Edge Functions or external HTTP endpoints on table events
|
|
- **Supabase ETL**: stream Postgres changes to external data warehouses in real time, with no pipelines
|
|
|
|
## Technical Details
|
|
|
|
- Engine: PostgreSQL (latest stable)
|
|
- Connection: direct Postgres connections (connection string), connection pooling via PgBouncer (Supavisor)
|
|
- Client libraries: JavaScript, Python, Dart (Flutter), Swift, Kotlin, C#
|
|
- Backups: automatic daily backups, Point-in-Time Recovery available as add-on
|
|
- Compute: configurable from Micro (2-core ARM) to 16XL+ (64-core ARM and above), with autoscaling options
|
|
|
|
## Links
|
|
|
|
- Documentation: https://supabase.com/docs/guides/database
|
|
- API Reference: https://supabase.com/docs/reference/javascript/select
|
|
- Dashboard: https://supabase.com/dashboard
|