mirror of
https://github.com/supabase/supabase.git
synced 2026-10-10 03:45:06 +03:00
Szymon MentelandClaude Sonnet 5
c832005c2c
Add a troubleshooting page for the hang / mismatched-row / invalid frontend message type failure mode caused by postgres.js's default query pipelining combined with Supavisor transaction mode's premature connection check-in. Link it from the pooling overview page and the postgres.js quickstart. Add "pipelining"/"pipelined" to the docs spelling dictionary so lint:mdx accepts the new content. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KpmtZWQTia6nfJfrYoh4gn
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.