mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 17:35:10 +03:00
docs: fixed multiple typos (#19928)
* docs: fixed typo integraions --> integrations * docs: fixed typo configration --> integrations * docs: fixed typo serivce --> service * docs: fixed typo thse --> these * docs: fixed typo infrastrusture --> infrastructure * docs: fixed typo organizatio --> organization * docs: fixed typo optimisation --> optimization * docs: fixed typo entitites --> entities * docs: fixed typo troubeshooting --> troubleshooting * prettier fix --------- Co-authored-by: Charis <26616127+charislam@users.noreply.github.com>
This commit is contained in:
ClarenceandCharis authored and GitHub committed
1 parent
c685d654b6
commit
734049feb8
9 files changed
+30
-30
No files matched your search
@@ -572,7 +572,7 @@ If you have multiple preview branches, each preview branch might contain differe
|
||||
|
||||
When a preview branch is merged into the production branch, it creates a schema drift between the production branch and the preview branches you haven't merged yet.
|
||||
|
||||
You can solve thse conflicts the way you would solve normal Git Conflicts: merge or rebase from your production Git branch to your preview Git branch. Since migrations are applied sequentially, ensure that migration files are timestamped correctly after the rebase. Changes that build on top of earlier changes should always have later timestamps.
|
||||
You can solve these conflicts the way you would solve normal Git Conflicts: merge or rebase from your production Git branch to your preview Git branch. Since migrations are applied sequentially, ensure that migration files are timestamped correctly after the rebase. Changes that build on top of earlier changes should always have later timestamps.
|
||||
|
||||
### Changing Production Branch
|
||||
|
||||
|
||||
@@ -264,7 +264,7 @@ const NEW_PROJECT_SERVICE_KEY = 'new-project-service-key-yyy'
|
||||
|
||||
### Transfer to a different organization
|
||||
|
||||
Note that project migration is for transferring your projects to different regions. If you need to move your project to a different organization without touching the infrastrusture, see [project transfers](/docs/guides/platform/project-transfer).
|
||||
Note that project migration is for transferring your projects to different regions. If you need to move your project to a different organization without touching the infrastructure, see [project transfers](/docs/guides/platform/project-transfer).
|
||||
|
||||
export const Page = ({ children }) => <Layout meta={meta} children={children} />
|
||||
|
||||
|
||||
@@ -130,7 +130,7 @@ There are a couple common patterns you can consider adding to your integration t
|
||||
|
||||
### Store API keys in env variables
|
||||
|
||||
Some integraions, e.g. like [Cloudflare Workers](/partners/integrations/cloudflare-workers) provide convenient access to the API URL and API keys to allow user to speed up development.
|
||||
Some integrations, e.g. like [Cloudflare Workers](/partners/integrations/cloudflare-workers) provide convenient access to the API URL and API keys to allow user to speed up development.
|
||||
|
||||
Using the management API, you can retrieve a project's API credentials using the [`/projects/{ref}/api-keys` endpoint](https://api.supabase.com/api/v1#/projects/getProjectApiKeys).
|
||||
|
||||
|
||||
@@ -19,26 +19,26 @@ Scopes are set when you [create an OAuth app](/docs/guides/platform/oauth-apps/b
|
||||
|
||||
## Available Scopes
|
||||
|
||||
| Name | Type | Description |
|
||||
| ---------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `Auth` | `Read` | Retrieve a project's auth configuration<br/>Retrieve a project's SAML SSO providers |
|
||||
| `Auth` | `Write` | Update a project's auth configuration<br/>Create, update, or delete a project's SAML SSO providers |
|
||||
| `Database` | `Read` | Retrieve the database configuration<br/>Retrieve SQL snippets<br/>Check if the database is in read-only mode<br/>Retrieve a database's SSL enforcement configuration<br/>Retrieve a database's schema typescript types |
|
||||
| `Database` | `Write` | Create a SQL query<br/>Enable database webhooks on the project<br/>Update the project's database configration<br/>Update a database's SSL enforcement configration<br/>Disable read-only mode for 15mins<br/>Retrieve the pgbouncer configuration<br/>Create a PITR backup for a database |
|
||||
| `Domains` | `Read` | Retrieve the custom domains for a project<br/>Retrieve the vanity subdomain configuration for a project |
|
||||
| `Domains` | `Write` | Activate, initialize, reverify, or delete the custom domain for a project<br/>Activate, delete or check the availability of a vanity subdomain for a project |
|
||||
| `Edge Functions` | `Read` | Retrieve information about a project's edge functions |
|
||||
| `Edge Functions` | `Write` | Create, update, or delete an edge function |
|
||||
| `Environment` | `Read` | Retrieve branches in a project |
|
||||
| `Environment` | `Write` | Create, update, or delete a branch |
|
||||
| `Organizations` | `Read` | Retrieve an organization's metadata<br/>Retrieve all members in an organization |
|
||||
| `Organizations` | `Write` | Create an organization |
|
||||
| `Projects` | `Read` | Retrieve a project's metadata<br/>Check if a project's database is eligible for upgrade<br/>Retrieve a project's network restrictions<br/>Retrieve a project's network bans |
|
||||
| `Projects` | `Write` | Create a project<br/>Upgrade a project's database<br/>Remove a project's network bans<br/>Update a project's network restrictions |
|
||||
| `Rest` | `Read` | Retrieve a project's PostgREST configuration |
|
||||
| `Rest` | `Write` | Update a project's PostgREST configuration |
|
||||
| `Secrets` | `Read` | Retrieve a project's API keys<br/>Retrieve a project's secrets<br/>Retrieve a project's pgsodium config |
|
||||
| `Secrets` | `Write` | Create or update a project's secrets<br/>Update a project's pgsodium configuration |
|
||||
| Name | Type | Description |
|
||||
| ---------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `Auth` | `Read` | Retrieve a project's auth configuration<br/>Retrieve a project's SAML SSO providers |
|
||||
| `Auth` | `Write` | Update a project's auth configuration<br/>Create, update, or delete a project's SAML SSO providers |
|
||||
| `Database` | `Read` | Retrieve the database configuration<br/>Retrieve SQL snippets<br/>Check if the database is in read-only mode<br/>Retrieve a database's SSL enforcement configuration<br/>Retrieve a database's schema typescript types |
|
||||
| `Database` | `Write` | Create a SQL query<br/>Enable database webhooks on the project<br/>Update the project's database configuration<br/>Update a database's SSL enforcement configuration<br/>Disable read-only mode for 15mins<br/>Retrieve the pgbouncer configuration<br/>Create a PITR backup for a database |
|
||||
| `Domains` | `Read` | Retrieve the custom domains for a project<br/>Retrieve the vanity subdomain configuration for a project |
|
||||
| `Domains` | `Write` | Activate, initialize, reverify, or delete the custom domain for a project<br/>Activate, delete or check the availability of a vanity subdomain for a project |
|
||||
| `Edge Functions` | `Read` | Retrieve information about a project's edge functions |
|
||||
| `Edge Functions` | `Write` | Create, update, or delete an edge function |
|
||||
| `Environment` | `Read` | Retrieve branches in a project |
|
||||
| `Environment` | `Write` | Create, update, or delete a branch |
|
||||
| `Organizations` | `Read` | Retrieve an organization's metadata<br/>Retrieve all members in an organization |
|
||||
| `Organizations` | `Write` | Create an organization |
|
||||
| `Projects` | `Read` | Retrieve a project's metadata<br/>Check if a project's database is eligible for upgrade<br/>Retrieve a project's network restrictions<br/>Retrieve a project's network bans |
|
||||
| `Projects` | `Write` | Create a project<br/>Upgrade a project's database<br/>Remove a project's network bans<br/>Update a project's network restrictions |
|
||||
| `Rest` | `Read` | Retrieve a project's PostgREST configuration |
|
||||
| `Rest` | `Write` | Update a project's PostgREST configuration |
|
||||
| `Secrets` | `Read` | Retrieve a project's API keys<br/>Retrieve a project's secrets<br/>Retrieve a project's pgsodium config |
|
||||
| `Secrets` | `Write` | Create or update a project's secrets<br/>Update a project's pgsodium configuration |
|
||||
|
||||
export const Page = ({ children }) => <Layout meta={meta} children={children} />
|
||||
|
||||
|
||||
@@ -78,7 +78,7 @@ Under the old system, you had different quotas for each service. i.e. on the Pro
|
||||
|
||||
Quotas and features are applied to your entire organization, independent of how many projects you launch within that organization. For billing purposes, we sum the usage across all projects in a monthly invoice.
|
||||
|
||||
Upgrading your organization to a paid plan means that you unlock the benefits of the paid plan for **all** projects within that organizatio - for example, no projects in your "Pro" organization will be paused. See [pricing page](https://supabase.com/pricing) for details on all plans.
|
||||
Upgrading your organization to a paid plan means that you unlock the benefits of the paid plan for **all** projects within that organization - for example, no projects in your "Pro" organization will be paused. See [pricing page](https://supabase.com/pricing) for details on all plans.
|
||||
|
||||
### Usage Items
|
||||
|
||||
@@ -143,7 +143,7 @@ Compute Credits do not apply to other usage fees like egress, database size, ...
|
||||
|
||||
Additionally, Compute Credits reset every month and do not accumulate, in case you're not running any projects.
|
||||
|
||||
With Legacy Billing, you used to pay $25 for every single Pro plan project in an organization. Previously, we gave you a free “Starter” instance on paid plans - we're now giving you $10 in Compute Credits instead, to cover the first instance. You end up not paying extra for the first project inside your paid plan organisation - just like before. In case you add a Compute Add-On to your first project, you also end up paying exactly the same as before.
|
||||
With Legacy Billing, you used to pay $25 for every single Pro plan project in an organization. Previously, we gave you a free “Starter” instance on paid plans - we're now giving you $10 in Compute Credits instead, to cover the first instance. You end up not paying extra for the first project inside your paid plan organization - just like before. In case you add a Compute Add-On to your first project, you also end up paying exactly the same as before.
|
||||
|
||||
## Legacy vs Organization-based Billing
|
||||
|
||||
|
||||
@@ -91,7 +91,7 @@ order by max_time desc
|
||||
limit 100;
|
||||
```
|
||||
|
||||
This query will show you statistics about queries ordered by the maximum execution time. It is similar to the query above ordered by calls, but this one highlights outliers that may have high executions times. Queries which have high or mean execution times are good candidates for optimisation.
|
||||
This query will show you statistics about queries ordered by the maximum execution time. It is similar to the query above ordered by calls, but this one highlights outliers that may have high executions times. Queries which have high or mean execution times are good candidates for optimization.
|
||||
|
||||
#### Most time consuming queries:
|
||||
|
||||
|
||||
@@ -10,8 +10,8 @@ The Supabase platform offers additional services (e.g. Storage) on top of the Po
|
||||
|
||||
However, these services assume a base level of access to their data, in order to e.g. be able to run migrations over it. Breaking these assumptions runs the risk of rendering these services inoperational for your project:
|
||||
|
||||
- all entitites under the `storage` schema are owned by `supabase_storage_admin`
|
||||
- all entitites under the `auth` schema are owned by `supabase_auth_admin`
|
||||
- all entities under the `storage` schema are owned by `supabase_storage_admin`
|
||||
- all entities under the `auth` schema are owned by `supabase_auth_admin`
|
||||
|
||||
It is possible for violations of these assumptions to not cause an immediate outage, but take effect at a later time when a newer migration becomes available.
|
||||
|
||||
|
||||
@@ -41,7 +41,7 @@ It's very important to send this file to your support contact at Supabase to com
|
||||
|
||||
## Step 5: Add service provider details [#add-service-provider-details]
|
||||
|
||||
Fill out these serivce provider details on the next screen.
|
||||
Fill out these service provider details on the next screen.
|
||||
|
||||
| Detail | Value |
|
||||
| -------------- | --------------------------------------------------- |
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
import Layout from '~/layouts/DefaultGuideLayout'
|
||||
|
||||
export const meta = {
|
||||
id: 'troubeshooting',
|
||||
id: 'troubleshooting',
|
||||
title: 'Troubleshooting',
|
||||
description: 'Diagnosing and fixing issues with your hosted Supabase project.',
|
||||
}
|
||||
|
||||
Reference in new issue
Block a user