mirror of
https://github.com/supabase/supabase.git
synced 2026-06-17 13:14:06 +08:00
608040b8cb
Contributes to DOCS-1052 ## 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? Resolves MDX linting errors related to "simple" where it applies. There was a couple cases that did not apply. For example, a product with "Simple" in the name. These changes are made in context, either by removing or using a more descriptive synonym like "minimal" or "basic". ## Tophatting 1. Read each of the diffs. 2. See that the text still makes sense in context. For extra due diligence, you can run `pnpm lint:mdx` locally and see the 'simple' errors that remain and whether they are worth addressing. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Summary by CodeRabbit * **Documentation** * Updated many guide, tutorial, and troubleshooting pages with clearer “basic”/“minimal” wording across setup steps, local testing instructions, security cautions, and RLS guidance. * Refined headings, example descriptions, and inline comments for consistency (including deployment, MCP, metrics API, and search/function phrasing). * Improved readability with small snippet formatting tweaks (whitespace plus import/comment ordering) and added a self-hosting debugging note for Envoy admin endpoints via a short-lived `curl` container. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Co-authored-by: Chris Chinchilla <chris.ward@supabase.io> Co-authored-by: Nik Richers <nrichers@gmail.com>
36 lines
1.7 KiB
Plaintext
36 lines
1.7 KiB
Plaintext
---
|
|
title: 'Server-Side Rendering'
|
|
subtitle: 'How SSR works with Supabase Auth.'
|
|
---
|
|
|
|
SSR frameworks move rendering and data fetches to the server, to reduce client bundle size and execution time.
|
|
|
|
Supabase Auth is fully compatible with SSR. You need to make a few changes to the configuration of your Supabase client, to store the user session in cookies instead of local storage. After setting up your Supabase client, follow the instructions for any flow in the How-To guides.
|
|
|
|
<Admonition type="tip">
|
|
|
|
Make sure to use the PKCE flow instructions where those differ from the implicit flow instructions. If no difference is mentioned, don't worry about this.
|
|
|
|
</Admonition>
|
|
|
|
## `@supabase/ssr`
|
|
|
|
We have developed an [`@supabase/ssr`](https://www.npmjs.com/package/@supabase/ssr) package for setting up the Supabase client. This package is currently in beta. Adoption is recommended but be aware that the API is still unstable and may have breaking changes in the future.
|
|
|
|
## Framework quickstarts
|
|
|
|
<div className="grid grid-cols-[repeat(auto-fit,minmax(300px,1fr))] gap-6 mb-6 not-prose">
|
|
<Link href="/guides/auth/server-side/nextjs" passHref>
|
|
<GlassPanel title="Next.js" background={false} icon="/docs/img/icons/nextjs-icon">
|
|
Automatically configure Supabase in Next.js to use cookies, making your user and their session
|
|
available on the client and server.
|
|
</GlassPanel>
|
|
</Link>
|
|
<Link href="/guides/auth/server-side/sveltekit" passHref>
|
|
<GlassPanel title="SvelteKit" background={false} icon="/docs/img/icons/svelte-icon">
|
|
Automatically configure Supabase in SvelteKit to use cookies, making your user and their
|
|
session available on the client and server.
|
|
</GlassPanel>
|
|
</Link>
|
|
</div>
|