dima/supabase

0 Fork 0

mirror of https://github.com/supabase/supabase.git synced 2026-10-06 09:55:06 +03:00

Files

T

History

bf633521b4 fix: add vector bucket local CLI section (#46646 )

## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.

YES

## What kind of change does this PR introduce?

Docs update

## What is the nee current behavior?

Added new section to explain how  vector buckets works locally

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Documentation**
* Added a "Local Development" guide for Vector Buckets covering
alpha-status cautions, local vs hosted behavior, steps to enable local
vector storage, declarative bucket configuration, and how to create
buckets for local testing.
* Updated site navigation to include the new Local Development guide in
the Storage → Vector docs.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Chris Chinchilla <chris.ward@supabase.io>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Chris Chinchilla <chris@chrischinchilla.com>

2026-06-12 08:09:31 +00:00

app

[DOCS-979] feat(Docs): Generate new markdown files for reference pages (#46727 )

2026-06-09 10:39:55 +02:00

components

fix: add vector bucket local CLI section (#46646 )

2026-06-12 08:09:31 +00:00

content

fix: add vector bucket local CLI section (#46646 )

2026-06-12 08:09:31 +00:00

data

chore(docs): clean dead code (#34096 )

2025-03-10 14:00:50 +01:00

docs

docs(self-hosted): update analytics guide (#46452 )

2026-06-03 10:48:14 +02:00

features

feat(docs) Add external link indicator for screenreader and visual (#46825 )

2026-06-11 08:59:08 +02:00

generator

chore: Use @/* as an alias for importing in-package files (#41607 )

2025-12-30 17:46:24 +01:00

hooks

feat: Implement telemetry on Search commands (#43563 )

2026-03-12 14:34:55 +01:00

internals

fix: Add /docs to Link hrefs on markdown script (#46798 )

2026-06-10 18:14:27 +02:00

layouts

chore: Migrate the monorepo to use Tailwind v4 (#45318 )

2026-04-30 10:53:24 +00:00

lib

fix(content): Remove map calls. Improve md extraction. (#46511 )

2026-06-01 15:55:06 +02:00

public

added myself to humans.txt (#46734 )

2026-06-12 10:00:39 +02:00

resources

fix: Throw error on mdx parsing (#46555 )

2026-06-01 16:45:45 +02:00

scripts

docs: update js sdk docs (2.108.1) (#46785 )

2026-06-09 19:17:12 +03:00

spec

feat: expose mgmt api v2 spec on official document (#46605 )

2026-06-04 14:53:26 +07:00

styles

chore: Migrate all apps to use Tailwind CSS configs (#45530 )

2026-05-07 17:18:15 +02:00

types

chore: migrate from next-mdx-remote to next-mdx-remote-client (#45149 )

2026-05-06 16:02:49 +02:00

.env.development

chore(docs): clean up environment variables (#36036 )

2025-05-29 16:35:26 -04:00

.gitignore

[DOCS-979] feat(Docs): Generate new markdown files for reference pages (#46727 )

2026-06-09 10:39:55 +02:00

codegen.ts

chore (content api): generate types from root schema (#35283 )

2025-05-02 11:25:35 -04:00

CONTRIBUTING.md

fix: Improve mermaid notation for markdown content and add contriburting instructions (#46679 )

2026-06-05 17:12:21 +02:00

declaration.d.ts

refactor(docs): turn auth error codes table into data file (#35857 )

2025-05-27 14:10:40 +00:00

DEVELOPERS.md

[DOCS-979] feat(Docs): Generate new markdown files for reference pages (#46727 )

2026-06-09 10:39:55 +02:00

eslint.config.cjs

chore: Migrate eslint for all apps to use flat config (#39486 )

2025-10-15 16:35:24 +02:00

instrumentation-client.ts

fix: correct grammar in comments and user-facing copy (#42918 )

2026-02-19 23:10:41 +08:00

instrumentation.ts

update: Add TS any checks to ratchet rules to further stop slipping (#40877 )

2025-12-02 14:18:21 +00:00

middleware.test.ts

fix(docs): negotiate /guides/* markdown via shared helper (#45432 )

2026-06-09 17:49:35 +08:00

middleware.ts

fix(docs): negotiate /guides/* markdown via shared helper (#45432 )

2026-06-09 17:49:35 +08:00

next-env.d.ts

Fix editing destination selected type (#41555 )

2025-12-23 19:36:00 +08:00

next.config.mjs

[DOCS-979] feat(Docs): Generate new markdown files for reference pages (#46727 )

2026-06-09 10:39:55 +02:00

package.json

[DOCS-979] feat(Docs): Generate new markdown files for reference pages (#46727 )

2026-06-09 10:39:55 +02:00

postcss.config.cjs

chore(docs): convert all scripts to esm (#35996 )

2025-05-29 15:44:55 -04:00

README.md

docs: Update contribution docs (#42402 )

2026-05-29 15:55:10 +02:00

sentry.edge.config.ts

chore(docs): turn off sentry sends for local dev (#35852 )

2025-05-22 15:23:27 -04:00

sentry.server.config.ts

chore(docs): turn off sentry sends for local dev (#35852 )

2025-05-22 15:23:27 -04:00

tsconfig.json

chore: Bump Typescript to v6 (#44204 )

2026-03-26 15:27:35 +01:00

turbo.jsonc

feat(docs): return page suggestions in markdown 404 pages (#45439 )

2026-05-05 08:40:44 +02:00

vercel.json

chore(docs): static assets cdn (#33347 )

2025-02-05 15:58:07 +00:00

vitest.config.ts

fix(docs): scope js-libs-update vitest run and make tests self-contained (#46737 )

2026-06-08 15:33:20 +03:00

vitest.globalSetup.ts

fix(docs): scope js-libs-update vitest run and make tests self-contained (#46737 )

2026-06-08 15:33:20 +03:00

vitest.setup.ts

feat(content api): add error endpoint (#35941 )

2025-05-29 15:39:47 -04:00

README.md

Reference Docs

Supabase Reference Docs

Maintainers

If you are a maintainer of any tools in the Supabase ecosystem, you can use this site to provide documentation for the tools & libraries that you maintain.

DocSpec

We use documentation specifications which can be used to generate human-readable docs.

OpenAPI: for documenting API endpoints.
SDKSpec (custom to Supabase): for SDKs and client libraries.
ConfigSpec (custom to Supabase): for configuration options.
CLISpec (custom to Supabase): for CLI commands and usage.

The benefit of using custom specifications is that we can generate many other types from a strict schema (eg, HTML and manpages). It also means that we can switch to any documentation system we want. On this site we use Next.js, but on Supabase's official website, we use a custom React site and expose only a subset of the available API for each tool.

Contributing

To contribute to docs, see the developers' guide and contributing guide.