diff --git a/apps/docs/pages/guides/auth/social-login/auth-slack.mdx b/apps/docs/pages/guides/auth/social-login/auth-slack.mdx index accf020f84d..38b3cf46b64 100644 --- a/apps/docs/pages/guides/auth/social-login/auth-slack.mdx +++ b/apps/docs/pages/guides/auth/social-login/auth-slack.mdx @@ -30,7 +30,7 @@ Setting up Slack logins for your application consists of 3 parts: ## Create a Slack OAuth app - Go to [api.slack.com](https://api.slack.com/apps). -- Click on `Create an App` +- Click on `Create New App` Under `Create an app...`: @@ -43,14 +43,17 @@ Under `App Credentials`: - Copy and save your newly-generated `Client ID` - Copy and save your newly-generated `Client Secret` -- Click `Permissions` -Under `Redirect URLs`: +Under the sidebar, select `OAuth & Permissions` and look for `Redirect URLs`: - Click `Add New Redirect URL` - Paste your `Callback URL` then click `Add` - Click `Save URLs` +Under `Scopes`: + +- Add the following scopes under the `User Token Scopes`: `profile`, `email`, `openid`. These scopes are the default scopes that Supabase Auth uses to request for user information. You can add any additional scopes that you may need as well. + ## Enter your Slack credentials into your Supabase Project diff --git a/apps/docs/pages/guides/resources/migrating-to-supabase/amazon-rds.mdx b/apps/docs/pages/guides/resources/migrating-to-supabase/amazon-rds.mdx index a4058763fd7..b81e0266558 100644 --- a/apps/docs/pages/guides/resources/migrating-to-supabase/amazon-rds.mdx +++ b/apps/docs/pages/guides/resources/migrating-to-supabase/amazon-rds.mdx @@ -93,5 +93,12 @@ pgloader config.load + + +- If you plan on migrating a database larger than 6 GB, we recommend [contacting support](https://app.supabase.com/support/new) to ensure that you'll have the proper disk size pre-provisioned. You can read more about how the disk is managed on Supabase on the [Database usage](/docs/guides/platform/database-size#disk-management). +- We also recommend upgrading to at least a [Large instance](/docs/guides/platform/compute-add-ons) for the migration (you can downgrade later) to avoid running out of IO-Budget. + + + export const Page = ({ children }) => export default Page diff --git a/apps/docs/pages/guides/resources/migrating-to-supabase/heroku.mdx b/apps/docs/pages/guides/resources/migrating-to-supabase/heroku.mdx index b2b5df2acd2..f2ed7478c6d 100644 --- a/apps/docs/pages/guides/resources/migrating-to-supabase/heroku.mdx +++ b/apps/docs/pages/guides/resources/migrating-to-supabase/heroku.mdx @@ -67,6 +67,13 @@ psql -h $SUPABASE_HOST -U postgres -f heroku_dump.sql Run `pg_dump --help` for a full list of options. + + +- If you plan on migrating a database larger than 6 GB, we recommend [contacting support](https://app.supabase.com/support/new) to ensure that you'll have the proper disk size pre-provisioned. You can read more about how the disk is managed on Supabase on the [Database usage](/docs/guides/platform/database-size#disk-management). +- We also recommend upgrading to at least a [Large instance](/docs/guides/platform/compute-add-ons) for the migration (you can downgrade later) to avoid running out of IO-Budget. + + + export const Page = ({ children }) => export default Page diff --git a/apps/docs/pages/guides/resources/migrating-to-supabase/render.mdx b/apps/docs/pages/guides/resources/migrating-to-supabase/render.mdx index 1e477b0e586..6d0eae2c6de 100644 --- a/apps/docs/pages/guides/resources/migrating-to-supabase/render.mdx +++ b/apps/docs/pages/guides/resources/migrating-to-supabase/render.mdx @@ -83,6 +83,13 @@ Run `pg_dump --help` for a full list of options. + + +- If you plan on migrating a database larger than 6 GB, we recommend [contacting support](https://app.supabase.com/support/new) to ensure that you'll have the proper disk size pre-provisioned. You can read more about how the disk is managed on Supabase on the [Database usage](/docs/guides/platform/database-size#disk-management). +- We also recommend upgrading to at least a [Large instance](/docs/guides/platform/compute-add-ons) for the migration (you can downgrade later) to avoid running out of IO-Budget. + + + export const Page = ({ children }) => export default Page diff --git a/apps/www/_blog/2023-04-13-supabase-auth-sso-pkce.mdx b/apps/www/_blog/2023-04-13-supabase-auth-sso-pkce.mdx index c1a4dfb36ea..b0ff0777bf7 100644 --- a/apps/www/_blog/2023-04-13-supabase-auth-sso-pkce.mdx +++ b/apps/www/_blog/2023-04-13-supabase-auth-sso-pkce.mdx @@ -225,6 +225,8 @@ export default async function handler(req: NextApiRequest, res: NextApiResponse) Since this is a major update that touches many of the authentication routes, we will roll it out gradually over the next few weeks. You will receive a notification in your dashboard when the feature is available for your project. Reach out to us if you want early access to this feature. +**Update**: Server-Side Auth (PKCE) is now available on all projects. Please refer to our [Server Side Auth Guide](https://supabase.com/docs/guides/auth/server-side-rendering) for further details on how to add PKCE to your project. + ## Native Apple login on iOS While PKCE support is great, that is not the only news for you mobile app developers out there. diff --git a/apps/www/_customers/mendableai.mdx b/apps/www/_customers/mendableai.mdx index ec0956cba7d..1a911c9f952 100644 --- a/apps/www/_customers/mendableai.mdx +++ b/apps/www/_customers/mendableai.mdx @@ -1,7 +1,7 @@ --- -title: Mendable.ai switches from Pinecone to Supabase for PostgreSQL vector embeddings. -name: Mendable.ai -description: How Mendable.ai boosts efficiency and accuracy of chat powered search for documentation using Supabase with pg_vector. +title: Mendable switches from Pinecone to Supabase for PostgreSQL vector embeddings. +name: Mendable +description: How Mendable boosts efficiency and accuracy of chat powered search for documentation using Supabase with pgvector. author: paul_copplestone author_title: Supabase author_url: https://github.com/kiwicopple @@ -21,19 +21,19 @@ stats: { stat: '00,000', label: Example stat }, ] misc: [{ label: 'Backed by', text: 'Y Combinator' }] -about: Mendable.ai is Chat Powered Search for Documentation. +about: Mendable is Chat Powered Search for Documentation. --- -[Mendable.ai](http://mendable.ai/) provides a chat-powered search engine for technical documentation. Their AI-powered search tool makes it easier for developers and other technical users to find relevant information in complex documentation. Users can simply ask questions in natural language, and the tool returns the most relevant answers. Mendable.ai's search engine also provides detailed analytics, which helps teams identify knowledge gaps and areas for improvement in their documentation. Mendable has integrated with some of the largest open source projects in the space such as Langchain and LlamaIndex. +[Mendable](http://mendable.ai/) provides a chat-powered search engine for technical documentation. Their AI-powered search tool makes it easier for developers and other technical users to find relevant information in complex documentation. Users can simply ask questions in natural language, and the tool returns the most relevant answers. Mendable's search engine also provides detailed analytics, which helps teams identify knowledge gaps and areas for improvement in their documentation. Mendable has integrated with some of the largest open source projects in the space such as Langchain and LlamaIndex. ## The Challenge -Mendable.ai was experiencing tremendous success, growing Weekly Active Users nearly 300% since March. They needed a tool to store and search through large amounts of vector data to improve the efficiency and accuracy of their similarity search operations. They tried Faiss, Weviate, and Pinecone, but found them to be expensive and not very intuitive, especially when it came to storing metadata along with the vectors. +Mendable was experiencing tremendous success, growing Weekly Active Users nearly 300% since March. They needed a tool to store and search through large amounts of vector data to improve the efficiency and accuracy of their similarity search operations. They tried Faiss, Weviate, and Pinecone, but found them to be expensive and not very intuitive, especially when it came to storing metadata along with the vectors. Why they chose Supabase: -Mendable.ai discovered that Supabase supports pgvector and found it to be a simple and cost-effective solution. They were impressed with the open source nature of Supabase, as well as its ability to store metadata alongside the vectors. They also appreciated the intuitive interface and ease of use. +Mendable discovered that Supabase supports pgvector and found it to be a simple and cost-effective solution. They were impressed with the open source nature of Supabase, as well as its ability to store metadata alongside the vectors. They also appreciated the intuitive interface and ease of use. - + We tried other vector databases - we tried Faiss, we tried Weviate, we tried Pinecone. We found them to be incredibly expensive and not very intuitive. If you’re just doing vector search they’re great, but if you need to store a bunch of metadata that becomes a huge pain. @@ -41,17 +41,17 @@ Mendable.ai discovered that Supabase supports pgvector and found it to be a simp ## What They Built -Using Supabase and pgvector, Mendable.ai was able to build a more efficient and accurate search function for their AI chatbot. By storing vector data alongside metadata in Supabase, Mendable.ai was able to quickly and easily search through their customers documentation to find the most relevant responses to queries. They found that Supabase's solution was just as performant as dedicated vector databases, but without the high cost. +Using Supabase and pgvector, Mendable was able to build a more efficient and accurate search function for their AI chatbot. By storing vector data alongside metadata in Supabase, Mendable was able to quickly and easily search through their customers documentation to find the most relevant responses to queries. They found that Supabase's solution was just as performant as dedicated vector databases, but without the high cost. ## The Results -Thanks to Supabase and pgvector, Mendable.ai was able to significantly improve the efficiency and accuracy of their Chat Powered Search for Documentation. They were able to build faster and more cost-effectively using Supabase’s open source stack. +Thanks to Supabase and pgvector, Mendable was able to significantly improve the efficiency and accuracy of their Chat Powered Search for Documentation. They were able to build faster and more cost-effectively using Supabase’s open source stack. ## Tech stack -Mendable.ai's tech stack includes React, Next.js, Express, Vercel, and Supabase. +Mendable's tech stack includes React, Next.js, Express, Vercel, and Supabase. - + We looked at the alternatives and chose Supabase because it’s open source, it’s simpler, and, for all the ways we need use it, Supabase has been just as performant - if not more performant - than the other vector databases. diff --git a/packages/ui/src/components/Command/AiCommand.tsx b/packages/ui/src/components/Command/AiCommand.tsx index 3a1fffafbe7..0db3f07a6f0 100644 --- a/packages/ui/src/components/Command/AiCommand.tsx +++ b/packages/ui/src/components/Command/AiCommand.tsx @@ -478,7 +478,7 @@ const AiCommand = () => {
{messages.length > 0 && !hasError && }
- - - {jsonSchema?.definitions && ( await refetch()} /> )} +
+ +
) : (
diff --git a/studio/components/to-be-cleaned/Docs/Pages/Introduction.tsx b/studio/components/to-be-cleaned/Docs/Pages/Introduction.tsx index a125f6c4006..c64f2f5457e 100644 --- a/studio/components/to-be-cleaned/Docs/Pages/Introduction.tsx +++ b/studio/components/to-be-cleaned/Docs/Pages/Introduction.tsx @@ -1,24 +1,6 @@ -import Image from 'next/image' import { AutoApiService } from 'data/config/project-api-query' -import { BASE_PATH } from 'lib/constants' import Snippets from '../Snippets' import CodeSnippet from '../CodeSnippet' -import { useTheme } from 'common' - -const libs = [ - { - name: 'Javascript', - url: 'https://supabase.com/docs/reference/javascript/introduction', - icon: 'javascript', - }, - { name: 'Flutter', url: 'https://supabase.com/docs/reference/dart/introduction', icon: 'dart' }, - { - name: 'Python', - url: 'https://supabase.com/docs/reference/python/introduction', - icon: 'python', - }, - { name: 'C#', url: 'https://supabase.com/docs/reference/csharp/introduction', icon: 'csharp' }, -] interface Props { autoApiService: AutoApiService @@ -26,84 +8,10 @@ interface Props { } export default function Introduction({ autoApiService, selectedLang }: Props) { - const { isDarkMode } = useTheme() - return ( <> -

Introduction

-
-
-

- This API provides an easy way to integrate with your Postgres database. The API - documentation below is specifically generated for your database. -

-

- This is an auto-generating API, so as you make changes to your database, this - documentation will change too. -

-

- Note: if you make changes to a field (column) name or type, the API interface for - those fields will change correspondingly. Therefore, please make sure to update your API - implementation accordingly whenever you make changes to your Supabase schema from the - graphical interface. -

- -
-

Read the reference documentation:

-
- {libs.map((lib, i) => ( - - {lib.name} - {lib.name} - - ))} -
-
-
-
- -

API URL

-
-
-

The API URL for your project.

-
-
- -
-
- -

Client Libraries

-
-

Your API consists of both a RESTful interface and a Realtime interface.

-

- For interacting with the Realtime streams, we provide client libraries that handle the - websockets. -

-
-