dima/supabase

0 Fork 0

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

Files

T

Taryn King bf415b64e6 chore(docs): add note for newer projects that use physical backups (#46653 )

## 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 current behavior?

Currently, this doc outlines how to restore a dashboard backup which
only applies to projects that still use logical backups. Newer projects
cannot follow this process.

## What is the new behavior?

Adds an admonition to direct users with projects that use physical
backups to the correct guide.

Keeping the legacy guide content for now for older projects that may
still be using logical backups.


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

## Summary by CodeRabbit

* **Documentation**
* Added clarification that dashboard backups are only available for
Supabase projects using logical backups. Projects using physical backups
are directed to refer to the CLI backup and restore guide instead.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-06-05 09:31:25 +02:00

app

fix: Rely on docs tag for wrappers content fetching (#46622 )

2026-06-04 10:41:42 +02:00

components

docs: Strengthen keys note (#46578 )

2026-06-04 11:56:23 +02:00

content

chore(docs): add note for newer projects that use physical backups (#46653 )

2026-06-05 09:31:25 +02: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: expose mgmt api v2 spec on official document (#46605 )

2026-06-04 14:53:26 +07: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(content): Remove map calls. Improve md extraction. (#46511 )

2026-06-01 15:55:06 +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

Update humans.txt - offboardings (#46635 )

2026-06-04 08:16:46 +02:00

resources

fix: Throw error on mdx parsing (#46555 )

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

scripts

docs: improve SDK automation build step on docs (#46163 )

2026-06-03 11:46:02 +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: improve SDK automation build step on docs (#46163 )

2026-06-03 11:46:02 +03:00

codegen.ts

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

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

CONTRIBUTING.md

chore(docs): migrate Admonition labels to titles (#46053 )

2026-05-18 19:00:09 +10: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: Update contribution docs (#42402 )

2026-05-29 15:55:10 +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.ts

feat(Docs): Implement Accept header for agents markdown requests (#43745 )

2026-03-13 13:32:40 +01:00

next-env.d.ts

Fix editing destination selected type (#41555 )

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

next.config.mjs

Revert "fix: move reference pages to hash navigation and apply redirect rules" (#46541 )

2026-06-01 13:00:36 +02:00

package.json

fix(docs): generate new reference pipeline output before embeddings (#46611 )

2026-06-03 13:08:36 +03: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

chore: prevent extraneous tsconfig errors in tests (#38718 )

2025-09-16 13:22:00 -04: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.