mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 17:35:10 +03:00
Katerina Skroumpelou
98e0572423
The embeddings workflow started failing after #46163 with `ENOENT: ... content/reference/javascript/v2/sections.json`. That PR routed the JS v2 search ingest through the new reference pipeline (`loadClientLibReferenceFromNewPipeline` in `apps/docs/scripts/search/sources/reference-doc.ts`), and updated `predev` and `prebuild` to run both `codegen:references` and `codegen:references:new`, but missed `preembeddings`. This chains `codegen:references:new` into `preembeddings` so `pnpm run embeddings` (and the `:nimbus` / `:refresh` variants that fan out to it) produces the new pipeline output before the search ingest reads it.
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.