mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 09:25:06 +03:00
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## Problem The Docs E2E link checker found broken links throughout docs, starting with `phone-login.mdx` pointing to `/docs/guides/cli/config` (404). Old links like `/docs/guides/cli/config` still work on the live site because `supabase.com` has redirects set up for them, but these links break on the docs preview site, which is what the E2E check tests against. These issues look clean on the live site, and I didn't catch them in my first pass because I was testing production instead of the preview. The E2E check only tests the ~20 pages a given PR happens to touch, so fixing the pages it flagged kept exposing more of the same problem one page at a time as each fix pulled in a new file. To stop chasing this incrementally, I cross-referenced every `/docs/guides/*` and `/docs/reference/*` redirect source in `apps/www/lib/redirects.js` against actual usage across all of `apps/docs`, and verified each candidate against the live preview. ## Solution Rather than updating the Docs E2E link checker, this PR resolves the links. **Why:** we own these docs, so keeping the links clean without redirects is keeping the house maintained. See [Broken Window Theory](https://blog.codinghorror.com/the-broken-window-theory/). Updated every link still using an old path to point straight at the current page instead of relying on a redirect. This covers old links like: - `/docs/guides/cli/config` → `/docs/guides/local-development/cli/config` - `/docs/guides/cli/getting-started` → `/docs/guides/local-development/cli/getting-started` - `/docs/guides/cli/local-development` → `/docs/guides/local-development/database-migrations` - `/docs/guides/cli/managing-environments` → `/docs/guides/deployment/managing-environments` - `/docs/guides/cli/seeding-your-database` → `/docs/guides/local-development/seeding-your-database` - bare `/docs/guides/cli` → `/docs/guides/local-development` - `/docs/guides/platform/compute-add-ons` → `/docs/guides/platform/compute-and-disk` - `/docs/guides/platform/shared-responsibility-model` → `/docs/guides/deployment/shared-responsibility-model` - `/docs/guides/database` → `/docs/guides/database/overview` - `/docs/reference/javascript`, `/docs/reference/dart`, `/docs/reference/kotlin`, `/docs/reference/python`, `/docs/reference/csharp` → their `/introduction` pages (the redirect's own destination, `/start`, turned out to be dead even on production — a separate bug in `redirects.js` I didn't touch here) - and about 35 more of the same pattern, listed in the commit messages Also fixed a handful of dead heading anchors found along the way (links that resolve to the right page but point at a `#section` that got renamed or moved), including the original `#bigquery` anchor and a few in `connecting-to-postgres.mdx` where content moved to its own dedicated page. Left alone on purpose: - `content/guides/cli.mdx` — this page has no route in the docs app at all (no `app/guides/cli/` directory), so it 404s even in production before the `www` redirect ever fires. Fixing its internal link wouldn't change that; it needs an actual routing/content decision, not a link fix. - A few candidates that already resolve fine as-is (`pg_partman`, bare `/docs/reference/api`, bare `/docs/reference/cli`) — confirmed via curl, left untouched. ## Manual testing 1. Confirmed every new link target actually exists by checking the destination file/page and matching heading anchors. 2. Cross-referenced every `/docs/guides/*` and `/docs/reference/*` redirect source in `apps/www/lib/redirects.js` against real usage in `apps/docs`, and curl-verified each old path (404) and new path (200) against the live PR preview before fixing it. 3. Ran the Docs E2E link checker locally against changed pages. 4. Spot-checked the original broken link from CI (`/docs/guides/cli/config`) to confirm it now points to a working page.
85 lines
2.3 KiB
Plaintext
85 lines
2.3 KiB
Plaintext
---
|
|
id: 'ai-vecs-python-client'
|
|
title: 'Python client'
|
|
subtitle: 'Manage unstructured vector stores in Postgres.'
|
|
breadcrumb: 'AI Quickstarts'
|
|
---
|
|
|
|
Supabase provides a Python client called [`vecs`](https://github.com/supabase/vecs) for managing unstructured vector stores. This client provides a set of useful tools for creating and querying collections in Postgres using the [pgvector](/docs/guides/database/extensions/pgvector) extension.
|
|
|
|
## Quick start
|
|
|
|
To see how Vecs works, use a local database. Make sure you have the Supabase CLI [installed](/docs/guides/local-development/cli/getting-started#installing-the-supabase-cli) on your machine.
|
|
|
|
### Initialize your project
|
|
|
|
Start a local Postgres instance in any folder using the `init` and `start` commands. Make sure you have Docker running!
|
|
|
|
```bash
|
|
# Initialize your project
|
|
supabase init
|
|
|
|
# Start Postgres
|
|
supabase start
|
|
```
|
|
|
|
### Create a collection
|
|
|
|
Inside a Python shell, run the following commands to create a new collection called "docs", with 3 dimensions.
|
|
|
|
```py
|
|
import vecs
|
|
|
|
# create vector store client
|
|
vx = vecs.create_client("postgresql://postgres:postgres@localhost:54322/postgres")
|
|
|
|
# create a collection of vectors with 3 dimensions
|
|
docs = vx.get_or_create_collection(name="docs", dimension=3)
|
|
```
|
|
|
|
### Add embeddings
|
|
|
|
Now we can insert some embeddings into our "docs" collection using the `upsert()` command:
|
|
|
|
```py
|
|
import vecs
|
|
|
|
# create vector store client
|
|
docs = vecs.get_or_create_collection(name="docs", dimension=3)
|
|
|
|
# a collection of vectors with 3 dimensions
|
|
vectors=[
|
|
("vec0", [0.1, 0.2, 0.3], {"year": 1973}),
|
|
("vec1", [0.7, 0.8, 0.9], {"year": 2012})
|
|
]
|
|
|
|
# insert our vectors
|
|
docs.upsert(vectors=vectors)
|
|
```
|
|
|
|
### Query the collection
|
|
|
|
You can now query the collection to retrieve a relevant match:
|
|
|
|
```py
|
|
import vecs
|
|
|
|
docs = vecs.get_or_create_collection(name="docs", dimension=3)
|
|
|
|
# query the collection filtering metadata for "year" = 2012
|
|
docs.query(
|
|
data=[0.4,0.5,0.6], # required
|
|
limit=1, # number of records to return
|
|
filters={"year": {"$eq": 2012}}, # metadata filters
|
|
)
|
|
```
|
|
|
|
## Deep dive
|
|
|
|
For a more in-depth guide on `vecs` collections, see [API](/docs/guides/ai/python/api).
|
|
|
|
## Resources
|
|
|
|
- Official Vecs Documentation: https://supabase.github.io/vecs/api
|
|
- Source Code: https://github.com/supabase/vecs
|