mirror of
https://github.com/supabase/supabase.git
synced 2026-10-06 01:45:10 +03:00
fix(prettier): additional formatting on newer changes
This commit is contained in:
Greg Richardson committed
1 parent
1c2609edfa
commit
1aaa45d501
4 files changed
+28
-29
No files matched your search
@@ -202,10 +202,7 @@ See the list of [tokens within a theme](https://github.com/supabase/auth-ui/blob
|
||||
import { createClient } from '@supabase/supabase-js'
|
||||
import { Auth } from '@supabase/auth-ui-react'
|
||||
|
||||
const supabase = createClient(
|
||||
'<INSERT PROJECT URL>',
|
||||
'<INSERT PROJECT ANON API KEY>'
|
||||
)
|
||||
const supabase = createClient('<INSERT PROJECT URL>', '<INSERT PROJECT ANON API KEY>')
|
||||
|
||||
const customTheme = {
|
||||
default: {
|
||||
@@ -239,7 +236,7 @@ const App = () => (
|
||||
<Auth
|
||||
supabaseClient={supabase}
|
||||
theme="default" // can also be "dark" or "evenDarker"
|
||||
appearance={{ theme: customTheme}}
|
||||
appearance={{ theme: customTheme }}
|
||||
/>
|
||||
)
|
||||
```
|
||||
|
||||
@@ -3,7 +3,7 @@ import Layout from '~/layouts/DefaultGuideLayout'
|
||||
export const meta = {
|
||||
id: 'using-environment-variables-in-config',
|
||||
title: 'Using environment variables in config.toml',
|
||||
description: 'How to use environment variables in config.toml with the Supabase CLI.'
|
||||
description: 'How to use environment variables in config.toml with the Supabase CLI.',
|
||||
}
|
||||
|
||||
The Supabase CLI is capable of utilizing environment variables stored in our project's root directory's `.env` file within the `config.toml` file.
|
||||
@@ -11,12 +11,14 @@ The Supabase CLI is capable of utilizing environment variables stored in our pro
|
||||
We can reference the environment variable by using the `env()` function.
|
||||
|
||||
Inside of our `.env` file we add the environment variable as we normally would
|
||||
|
||||
```env
|
||||
GITHUB_CLIENT_ID=""
|
||||
GITHUB_SECRET=""
|
||||
```
|
||||
|
||||
And then reference them inside of our `config.toml`
|
||||
|
||||
```toml
|
||||
[auth.external.github]
|
||||
enabled = true
|
||||
|
||||
@@ -3,7 +3,8 @@ import Layout from '~/layouts/DefaultGuideLayout'
|
||||
export const meta = {
|
||||
id: 'exhaust-cpu',
|
||||
title: 'High CPU Usage',
|
||||
description: 'Learn what high CPU usage could mean for your Supabase instance and what could have caused it.',
|
||||
description:
|
||||
'Learn what high CPU usage could mean for your Supabase instance and what could have caused it.',
|
||||
}
|
||||
|
||||
Learn what high CPU usage could mean for your Supabase instance and what could have caused it.
|
||||
@@ -14,9 +15,9 @@ Every Supabase project runs in its dedicated virtual machine. Your instance will
|
||||
|
||||
High CPU usage could come with a range of issues:
|
||||
|
||||
* slower queries
|
||||
* disruption of daily backup routines
|
||||
* in rare cases, your instance may become unresponsive
|
||||
- slower queries
|
||||
- disruption of daily backup routines
|
||||
- in rare cases, your instance may become unresponsive
|
||||
|
||||
Moreover, your instance might not be able to handle future traffic spikes if it already has a high CPU usage.
|
||||
|
||||
@@ -32,16 +33,16 @@ It is also possible to monitor your resources and set up alerts using Prometheus
|
||||
|
||||
Everything you do with your Supabase project requires compute. Hence, there can be many reasons for high CPU usage. Here are some common ones:
|
||||
|
||||
* __Query performance:__ Queries that take a long time to complete (>1 second) as well as excessive amounts of querying can put a strain on the CPU. Check our guide on [examining query performance](https://supabase.com/docs/guides/platform/performance#examining-query-performance).
|
||||
* __Missing indexes:__ Your database might have to scan through a large amount of data to find the information it needs. Creating indexes helps your database find data faster. Learn more about indexes [here](https://supabase.com/docs/guides/database/postgres/indexes).
|
||||
* __Unsuitable compute:__ The instance size of your Supabase project might not be suitable for your application as you might have more traffic or run resource-intensive operations.
|
||||
- **Query performance:** Queries that take a long time to complete (>1 second) as well as excessive amounts of querying can put a strain on the CPU. Check our guide on [examining query performance](https://supabase.com/docs/guides/platform/performance#examining-query-performance).
|
||||
- **Missing indexes:** Your database might have to scan through a large amount of data to find the information it needs. Creating indexes helps your database find data faster. Learn more about indexes [here](https://supabase.com/docs/guides/database/postgres/indexes).
|
||||
- **Unsuitable compute:** The instance size of your Supabase project might not be suitable for your application as you might have more traffic or run resource-intensive operations.
|
||||
|
||||
## Solving high CPU usage
|
||||
|
||||
There are two ways to solve high CPU:
|
||||
|
||||
1. __Optimize performance:__ Get more out of your instance's resources by optimizing your usage. Have a look at our [performance tuning guide](https://supabase.com/docs/guides/platform/performance#examining-query-performance) and our [production readiness guide](https://supabase.com/docs/guides/platform/going-into-prod#performance).
|
||||
2. __Upgrade your compute:__ You can get a Compute Add-on for your project. Follow [this link](https://app.supabase.com/project/_/settings/billing/update/pro) and select your project to see your upgrade options.
|
||||
1. **Optimize performance:** Get more out of your instance's resources by optimizing your usage. Have a look at our [performance tuning guide](https://supabase.com/docs/guides/platform/performance#examining-query-performance) and our [production readiness guide](https://supabase.com/docs/guides/platform/going-into-prod#performance).
|
||||
2. **Upgrade your compute:** You can get a Compute Add-on for your project. Follow [this link](https://app.supabase.com/project/_/settings/billing/update/pro) and select your project to see your upgrade options.
|
||||
|
||||
export const Page = ({ children }) => <Layout meta={meta} children={children} />
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ toc_depth: 3
|
||||
|
||||
Brace yourself, this is one of the most feature-packed Beta Updates we've published so far.
|
||||
|
||||
[Launch Week 7](https://supabase.com/launch-week) was a massive success with great feedback from the community. We also gave away lots of mechanical keyboards, including the Hackathon winner which we announce here!
|
||||
[Launch Week 7](https://supabase.com/launch-week) was a massive success with great feedback from the community. We also gave away lots of mechanical keyboards, including the Hackathon winner which we announce here!
|
||||
|
||||
## Day 1 - Supabase Logs: open source logging server
|
||||
|
||||
@@ -59,7 +59,7 @@ Supabase Studio got a major upgrade that goes from redesigns to improved develop
|
||||
[Blog Post](https://supabase.com/blog/supabase-studio-2.0)\
|
||||
[Video overview](https://www.youtube.com/watch?v=0rcNqHt5KWU)
|
||||
|
||||
## Community highlights
|
||||
## Community highlights
|
||||
|
||||
|
||||
|
||||
@@ -71,24 +71,23 @@ Our community defines us. We're honored to work with, sponsor, and support incre
|
||||
|
||||
|
||||
|
||||
[database.dev](https://database.dev/) fills the same role for PostgreSQL as `npm` for JavaScript or `pip` for Python, it enables publishing libraries and applications for repeatable deployment. Our goal is to create an open ecosystem for packaging and discovering SQL.
|
||||
[database.dev](https://database.dev/) fills the same role for PostgreSQL as `npm` for JavaScript or `pip` for Python, it enables publishing libraries and applications for repeatable deployment. Our goal is to create an open ecosystem for packaging and discovering SQL.
|
||||
|
||||
[Blog post](https://supabase.com/blog/dbdev)
|
||||
|
||||
## More product announcements
|
||||
|
||||
- Trusted Language Extensions for Postgres. [[Blog post]](https://supabase.com/blog/pg-tle)
|
||||
- What's New in pg_graphql v1.2. [[Blog post]](https://supabase.com/blog/whats-new-in-pg-graphql-v1-2)
|
||||
- GitHub Discussions are now a new knowledge source for search & AI (Troubleshooting category only for now). [[Check it out]](https://supabase.com/docs)
|
||||
- New API report with routing information for each chart, making it easier to debug API calls. [[PR]](https://github.com/supabase/supabase/pull/14063)
|
||||
- Trusted Language Extensions for Postgres. [[Blog post]](https://supabase.com/blog/pg-tle)
|
||||
- What's New in pg_graphql v1.2. [[Blog post]](https://supabase.com/blog/whats-new-in-pg-graphql-v1-2)
|
||||
- GitHub Discussions are now a new knowledge source for search & AI (Troubleshooting category only for now). [[Check it out]](https://supabase.com/docs)
|
||||
- New API report with routing information for each chart, making it easier to debug API calls. [[PR]](https://github.com/supabase/supabase/pull/14063)
|
||||
- Storage permission changes: the developer role is now allowed to update the storage settings (previously was only owner and admin). [[PR]](https://github.com/supabase/supabase/pull/13883)
|
||||
|
||||
|
||||
## Launch Week 7 Hackathon winners
|
||||
|
||||
|
||||
|
||||
The community is loving `pgvector` to build AI apps so we decided to make it part of the traditional Launch Week Hackathon. The quality of the apps was out of this world, it wasn't easy, but in the end, we selected [Page Assist](https://github.com/n4ze3m/page-assist) - by [@n4ze3m ](https://twitter.com/n4ze3m)as the winner of the Best Overall Project.
|
||||
The community is loving `pgvector` to build AI apps so we decided to make it part of the traditional Launch Week Hackathon. The quality of the apps was out of this world, it wasn't easy, but in the end, we selected [Page Assist](https://github.com/n4ze3m/page-assist) - by [@n4ze3m ](https://twitter.com/n4ze3m)as the winner of the Best Overall Project.
|
||||
|
||||
[Full list of Winners](https://supabase.com/blog/launch-week-7-hackathon-winners)
|
||||
|
||||
@@ -106,12 +105,12 @@ With Supabase's pg_vector, Mendable.ai could build a more cost-effective solutio
|
||||
|
||||
|
||||
|
||||
- FlutterFlow now supports Supabase Authentication. [Video guide](https://www.youtube.com/watch?v=tL-sLPfWzVE)
|
||||
- Supabase + ClickHouse: Combining the Best of the OLTP and OLAP Worlds. [Webinar](https://www.youtube.com/watch?v=LDWEsw41Zko)
|
||||
- Our friend Guillaume put together the most incredible course about Supabase, with the in and outs of the platform. [Full course](https://www.youtube.com/watch?v=8DTOTT7q0XA)
|
||||
- Supabase + LangChain starter template for building full stack AI apps. [Template](https://github.com/langchain-ai/langchain-template-supabase)
|
||||
- FlutterFlow now supports Supabase Authentication. [Video guide](https://www.youtube.com/watch?v=tL-sLPfWzVE)
|
||||
- Supabase + ClickHouse: Combining the Best of the OLTP and OLAP Worlds. [Webinar](https://www.youtube.com/watch?v=LDWEsw41Zko)
|
||||
- Our friend Guillaume put together the most incredible course about Supabase, with the in and outs of the platform. [Full course](https://www.youtube.com/watch?v=8DTOTT7q0XA)
|
||||
- Supabase + LangChain starter template for building full stack AI apps. [Template](https://github.com/langchain-ai/langchain-template-supabase)
|
||||
- Creating a Books Tracker App with .NET MAUI and Supabase. [Article](https://hackernoon.com/creating-a-books-tracker-app-with-net-maui-and-supabase)
|
||||
- Vanta Case Study - Supabase turns trust into a revenue-generating opportunity with Vanta. [Case Study](https://www.vanta.com/customers/supabase)
|
||||
- Vanta Case Study - Supabase turns trust into a revenue-generating opportunity with Vanta. [Case Study](https://www.vanta.com/customers/supabase)
|
||||
|
||||
## Meme Zone
|
||||
|
||||
|
||||
Reference in new issue
Block a user