mirror of
https://github.com/supabase/supabase.git
synced 2026-07-04 09:44:19 +08:00
d91ea9d4e2
* Clearup keys and connection instructions in web getting started guides * Update apps/docs/content/_partials/project_setup.mdx Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update apps/docs/content/_partials/project_setup.mdx Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * prettier * second try * Fix keys for getting started section * Updated keys for auth section, SSR aside * Remove mention of dropdowns for now --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
13 lines
978 B
Plaintext
13 lines
978 B
Plaintext
{/* TODO: How to completely consolidate partials? */}
|
|
|
|
<Admonition type="note" title="Changes to API keys">
|
|
|
|
Supabase is changing the way keys work to improve project security and developer experience. You can [read the full announcement](https://github.com/orgs/supabase/discussions/29260), but in the transition period, you can use both the current `anon` and `service_role` keys and the new publishable key with the form `sb_publishable_xxx` which will replace the older keys.
|
|
|
|
To get the key values, open [the API Keys section of a project's Settings page](/dashboard/project/_/settings/api-keys/) and do the following:
|
|
|
|
- **For legacy keys**, copy the `anon` key for client-side operations and the `service_role` key for server-side operations from the **Legacy API Keys** tab.
|
|
- **For new keys**, open the **API Keys** tab, if you don't have a publishable key already, click **Create new API Keys**, and copy the value from the **Publishable key** section.
|
|
|
|
</Admonition>
|