{error.message}
} -Protected content
+ return (
+ <>
+ Protected content for {user.email}
+ Data fetched with provider token:
+{JSON.stringify(allRepos, null, 2)}
+ user:
+{JSON.stringify(user, null, 2)}
+
+ )
}
export const getServerSideProps = withPageAuth({
redirectTo: '/',
- async getServerSideProps(ctx) {
- // Retrieve provider_token from cookies
- const provider_token = ctx.req.cookies['sb-provider-token']
- // Get logged in user's third-party id from metadata
- const { user } = await getUser(ctx)
- const userId = user?.user_metadata.provider_id
- const profile: Profile = await (
- await fetch(`https://api.example.com/users/${userId}`, {
- method: 'GET',
- headers: {
- Authorization: `Bearer ${provider_token}`,
- },
- })
+ async getServerSideProps(ctx, supabase) {
+ const {
+ data: { session },
+ error,
+ } = await supabase.auth.getSession()
+ if (error) {
+ throw error
+ }
+ if (!session) {
+ return { props: {} }
+ }
+
+ // Retrieve provider_token & logged in user's third-party id from metadata
+ const { provider_token, user } = session
+ const userId = user.user_metadata.user_name
+
+ const allRepos = await (
+ await fetch(
+ `https://api.github.com/search/repositories?q=user:${userId}`,
+ {
+ method: 'GET',
+ headers: {
+ Authorization: `token ${provider_token}`,
+ },
+ }
+ )
).json()
- return { props: { profile } }
+
+ return { props: { allRepos, user } }
},
})
```
@@ -355,6 +426,7 @@ export const config = {
```
- The `supabaseClient` and `supabaseServerClient` have been removed in favor of the `createBrowserSupabaseClient` and `createServerSupabaseClient` methods. This allows you to provide the CLI-generated types to the client:
+
```js
// client-side
import type { Database } from 'types_db';
@@ -373,12 +445,14 @@ export const config = {
res.status(200).json({ name: user?.name ?? '' })
}
```
+
- The `UserProvider` has been replaced by the `SessionContextProvider`. Make sure to wrap your `pages/_app.js` componenent with the `SessionContextProvider`. Then, throughout your application you can use the `useSessionContext` hook to get the `session` and the `useSupabaseClient` hook to get an authenticated `supabaseClient`.
- The `useUser` hook now returns the `user` object or `null`.
- Usage with TypeScript: You can pass types that were [generated with the Supabase CLI](/docs/reference/javascript/typescript-support#generating-types) to the Supabase Client to get enhanced type safety and auto completion:
+
```js
// Creating a new supabase client object:
- import { Database } from '../db_types';
+ import { Database } from '../database.types';
const [supabaseClient] = useState(() =>
createBrowserSupabaseClient+ +## Auth + +### Email & Password Logins + +Build email logins for your application or website. [Docs](/docs/guides/auth/auth-email). + +### Magic Links + +Build passwordless logins for your application or website.[Docs](/docs/guides/auth/auth-magic-link). + +### Social Logins + +Provide social logins - everything from Apple, to GitHub, to Slack. [Docs](/docs/guides/auth/auth-apple). + +### Phone Logins + +Provide phone logins using a 3rd-party SMS provider. [Docs](/docs/guides/auth/auth-twilio). + +### Row Level Security + +Control the data each user can access with Postgres Policies. [Docs](/docs/guides/auth/row-level-security). + +### Serverside Auth Helpers + +Helpers for implementing user authentication in popular frameworks like [Next.js](/docs/guides/auth/auth-helpers/nextjs) and [SvelteKit](/docs/guides/auth/auth-helpers/sveltekit) + +### Auth UI Kit + +Build login and registration pages with custom themes. [Docs](/docs/guides/auth/auth-helpers/auth-ui). + +
+ +## APIs & Client libraries + +### Auto-generated REST API + +RESTful APIs are autogenerated from your database, without a single line of code. [Docs](/docs/guides/api#rest-api-overview). + +### Auto-generated GraphQL API + +Fast GraphQL APIs using our custom Postgres GraphQL extension. [Docs](/docs/guides/api#graphql-api-overview). + +### Realtime Database changes + +Receive your database changes through websockets. [Docs](/docs/guides/realtime/postgres-cdc). + +### User Broadcasting + +Send messages between connected users through websockets. [Docs](/docs/guides/realtime#broadcast). + +### User Presence + +Synchronize shared state across your users, including online status and typing indicators. [Docs](/docs/guides/realtime#presence). + +### Client libraries + +Official client libraries for [JavaScript](/docs/reference/javascript/) and [Dart](/docs/reference/dart). +Unofficial libraries [supported by the community](https://github.com/supabase-community#client-libraries). + +
+ +## File Storage + +### Large File storage + +Supabase Storage makes it simple to store and serve large files. [Docs](/docs/guides/storage). + +### Storage CDN + +Cache large files using the Supabase CDN. [Docs](/docs/guides/storage-cdn). + +
+ +## Edge Functions + +### Deno Edge Functions + +Globally distributed TypeScript functions to execute custom business logic. [Docs](/docs/guides/functions). + +
+ +## Project Managment + +### CLI + +Use our CLI to develop your project locally and deploy to the Supabase Platform. [Docs](/docs/reference/cli). + +### Admin API + +Manage your projects programmatically. [Docs](/docs/reference/api). + +
+ +## Feature Status + +Both Postgres and the Supabase Platform are production-ready. Some tools we offer on top of Postgres are still under development. + +| Product | Feature | Stage | +| -------------------------- | ---------------------- | ------- | +| Database | Postgres | `GA` | +| Database | Triggers | `GA` | +| Database | Functions | `GA` | +| Database | Extensions | `GA` | +| Database | Full Text Search | `GA` | +| Database | Webhooks | `alpha` | +| Database | Point-in-Time Recovery | `alpha` | +| Database | Vault | `alpha` | +| Studio | | `GA` | +| Realtime | Postgres CDC | `beta` | +| Realtime | Broadcast | `alpha` | +| Realtime | Presence | `alpha` | +| Storage | Backend (S3) | `GA` | +| Storage | API | `beta` | +| Storage | CDN | `beta` | +| Edge Functions | | `beta` | +| Auth | OAuth Providers | `beta` | +| Auth | Passwordless | `beta` | +| Auth | Next.js Auth Helpers | `alpha` | +| Auth | SvelteKit Auth Helpers | `alpha` | +| Admin API | | `beta` | +| CLI | | `beta` | +| Client Library: JavaScript | | `GA` | +| Client Library: Dart | | `beta` | diff --git a/apps/reference/docs/guides/integrations/dhiwise.mdx b/apps/reference/docs/guides/integrations/dhiwise.mdx new file mode 100644 index 00000000000..15b4110ed1e --- /dev/null +++ b/apps/reference/docs/guides/integrations/dhiwise.mdx @@ -0,0 +1,175 @@ +--- +id: dhiwise +title: 'DhiWise' +description: 'Get started with Supabase and DhiWise. Convert your Figma designs into Flutter apps, store data, and authenticate your users' +--- +import select from "/img/guides/integrations/dhiwise/select.png" +import create from "/img/guides/integrations/dhiwise/create.png" + +This guide explains how to connect Supabase backend to DhiWise Flutter application quickly. + +[DhiWise](https://www.dhiwise.com/) is a Developer tool to convert Figma designs into React and Flutter applications. It lets you quickly integrate Databases and APIs into your React and Flutter Apps. + +If you don't have a DhiWise account, create one [here](https://app.dhiwise.com). + +DhiWise supports easy Supabase Integration in just five steps. + +Let's get started! + +## Step 1: SignIn to Supabase + +Go to [Supabase](https://supabase.com/), Click `Sign In`, and create a new account by authenticating with **GitHub**. If you already have an account, you will be logged in. + +## Step 2: Create a new project in Supabase + +Click on `New project` from the Dashboard and select an organization. If you don't have an organization, create one using `+ New organization.` + +- Give your Supabase project a `name.` +- Enter a secure `Database Password.` +- Choose the `region` where your app's backend is hosted. +- Click `Create new project.` + + + +## Step 3: Find the API key and URL + +Once your project is created, you can access the API Key and URL string, Or if you already have an account go to your `organization-> app-> settings-> API`. + + + +## Step 4: Integrations + +There are two ways you can integrate Supabase into your DhiWise Flutter applications. + +### Authentication + +You can integrate `Supabase Email/Password SignUp` or `Supabase Email/Password SignIn` on your components. + +- Open the screen of your flutter application +- Go to the component on which you want to add authentication +- on the `onClick` method - select `authentication` +- From the list, If you want SignUp - select `SignUp with Email/Password`; otherwise, select `SignIn with Email/Password` from Supabase Auth section + + + +And that's it. Supabase authentication will be added to the selected component. + +After downloading the application source code, +1. Add Supabase URL and Supabase public key inside ***lib/core/utils/initial_bindings*** file. +2. For additional details, refer ***https://supabase.com/docs/guides/with-flutter*** + +### Working with Data + +When you first integrate Supabase in your DhiWise Flutter application, You will be asked to add [Supabase auth key and URL](##step-3-find-the-api-key-and-url). When you add them, all the tables available in your Supabase project will be synced in DhiWise. You can integrate Select and Create queries on your Flutter screen for a particular table in DhiWise. + +
Select records
+ +#### **Step 1:** +Select the screen from the screen list where you want to integrate Supabase. + +#### **Step 2:** +Next, go to the view where you want to add Integration, and from the suggestion box for the `onClick` property, choose `Supabase integration,` which will take you to the Integration screen. Where you will be asked to `Enter function name.` Enter the name of your function and click `Submit.` + +#### **Step 3:** +After submitting the function name, you will be asked to select a type of Supabase integration. To retrieve data from Supabase, choose `select.` + +#### **Step 4:** +Next, select the table from which you want to fetch records from the listed Tables. + +#### **Step 5:** +Select the type of integration + +| Type | Description | +| --- | --- | +| **Single** | Used to fetch a single record from the database. | +| **Multiple** | Used to fetch multiple records from the database. | + +:::info +For Multiple types, you need to set `data limit,` `order by, and `order.` +::: + +#### **Step 6:** +You will be redirected to the API Integration screen, where you can set request and response. + +For request binding, the below types are supported. Also, Select the operator for comparison before moving forward. + +| Type | Description | +| --- | --- | +| **View** | Select any component from your screen. | +| **Constant** | Select a constant you've created in your app. | +| **Get from preference** | Select the key you want to fetch from preference. | +| **Navigation argument** | Select data that's been passed from one screen to another. | + +For response binding, the below types are supported. + +| Type | Description | +| --- | --- | +| **View** | Select any component from the screen. | +| **Save to preference** | Storing the data to preference. | + +#### **Select 7:** +`Handle action` - Select the action you wish to take once the Supabase call has either been accepted successfully or refused due to an error. + +Available action for On success and On error are, + +1. [Show Alert](https://docs.dhiwise.com/docs/flutter/show-alert) +2. [Navigation](https://docs.dhiwise.com/docs/flutter/navigation) + +#### **Step 8:** +Finally, you have added Supabase to your application to fetch records on your screen! + +:::tip Example +Suppose you want to fetch records from Supabase and populate the item list on your screen. You can integrate Supabase as discussed above and bind the response with your list view. +::: + +Create records
+ +#### **Step 1:** +Choose the screen you wish to integrate Supabase for from the list of screens. + +#### **Step 2:** +Next, switch to the component you want to add Integration, and on the `onClick` property, choose `Supabase integration,` which will take you to its integration screen, where you will be asked to **Enter function name**, which will be used in generated code. Enter the name for it and click `Submit` + +#### **Step 3:** +After submitting the function name, you will be asked to select a type of Supabase integration. For example, to create a record in Supabase, choose `Create.` + +#### **Step 4:** +Next, select the table where you want to create a record from the listed Tables. + +#### **Step 5:** +If you want to create a Single record, Select **Select**. Otherwise, **Multiple**. + +#### **Step 6:** +Now, you will be redirected to the API Integration screen, where you can set request and response. + +For request binding, the below types are supported. + +| Type | Description | +| --- | --- | +| **View** | Select any component from the screen | +| **Constant** | Select a constant you've created in your app.| +| **Get from preference** | Select the key you want to fetch from preference. | +| **Navigation argument** | Select data that's been passed from one screen to another. | + +For response binding, the below types are supported. + +| Type | Description | +| --- | --- | +| **View** | Select any component from the screen | +| **Save to preference** | Storing the data to preference. | + +#### **Select 7:** +`Handle action` - Select the action you wish to take once the Supabase call has either been accepted successfully or refused due to an error. + +Available action for On success and On error are, + +1. [Show Alert](https://docs.dhiwise.com/docs/flutter/show-alert) +2. [Navigation](https://docs.dhiwise.com/docs/flutter/navigation) + +#### **Step 9:** +Finally, you have added Supabase to your application to create records from your screen data! + +## Resources + +- [DhiWise Official Website](https://dhiwise.com) +- [DhiWise Documentation](https://docs.dhiwise.com) \ No newline at end of file diff --git a/apps/reference/docs/guides/integrations/integrations.mdx b/apps/reference/docs/guides/integrations/integrations.mdx new file mode 100644 index 00000000000..9fdf5c6fa2d --- /dev/null +++ b/apps/reference/docs/guides/integrations/integrations.mdx @@ -0,0 +1,34 @@ +--- +id: integrations +title: 'Supabase Marketplace' +description: 'Integrations and Partners' +--- + +The Supabase Marketplace brings together all the tools you need to extend your Supabase project. This includes: + +- [Experts](https://supabase.com/partners/experts) - partners to help you build and support your Supabase project. +- [Integrations](https://supabase.com/partners/integrations) - extend your projects with external Auth, Caching, Hosting, and Low-code tools. + +## Build an integration + +Supabase provides several integration points: + +- The [Postgres connection](/docs/guides/database/connecting-to-postgres). Anything that works with Postgres also works with Supabase projects. +- The [Project REST API](/docs/guides/api#rest-api) & client libraries. +- The [Project GraphQL API](/docs/guides/api#graphql-api). +- The [Platform API](/docs/reference/api). + +## List your integration + +[Apply to the Partners program](https://supabase.com/partners/integrations#become-a-partner) to list your integration in the Partners marketplace and in the Supabase docs. + +Integrations are assessed on the following criteria: + +- **Business viability** + While we welcome everyone to built an integration, we only list companies that are deemed to be long-term viable. This includes an official business registration and bank account, meaningful revenue, or Venture Capital backing. We require this criteria to ensure the health of the marketplace. +- **Compliance** + Integrations should not infringe on the Supabase brand/trademark. In short, you cannot use "Supabase" in the name. As the listing appears on the Supabase domain, we don't want to mislead developers into thinking that an integration is an official product. +- **Service Level Agreements** + All listings are required to have their own Terms and Conditions, Privacy Policy, and Acceptable Use Policy, and the company must have resources to meet their SLAs. +- **Maintainability** + All integrations are required to be maintained and functional with Supabase, and the company may be assessed on your ability to remain functional over a long time horizon. diff --git a/apps/reference/docs/guides/integrations/keyri.mdx b/apps/reference/docs/guides/integrations/keyri.mdx new file mode 100644 index 00000000000..936db47bad8 --- /dev/null +++ b/apps/reference/docs/guides/integrations/keyri.mdx @@ -0,0 +1,149 @@ + +id: keyri +title: 'Keyri' +description: 'QR authentication for an easy and flexible biometric solution across all platforms.' +--- + +Keyri can be used to incorporate sign-in-with-QR functionality into your Supabase app, allowing users to scan a QR code on your web app with your mobile app and be instantly logged into the web app without having to input any credentials. + +Configuration is split into Web and Mobile components. On web, the Keyri QR Widget needs to be installed along with an event listener, and in your mobile app, install the Keyri SDK and pass into it the user's refresh token when sign-in-with-QR is initiated. When the refresh token lands in your web app, it's passed into Supabase's `setSession()` method. + +# Sign up for Keyri + +First make a free account on the Keyri dashboard (
+
+
+```
+
+Next, for the same login view, set up an event listener to pick up the session token that the iFrame emits when the QR code is scanned by your app.
+
+```javascript
+useEffect(() => {
+ window.addEventListener('message', async (evt) => {
+ if (evt.data.keyri && evt.data.data && document.location.origin == evt.origin) {
+ const { data } = evt;
+ if (!data.error) {
+ let refresh_token = JSON.parse(data.data).refreshToken;
+ await handleQrLogin(refresh_token);
+ } else if (data.error) {
+ console.log(`Keyri error: ${data.message}`);
+ }
+ }
+});
+```
+
+That's it!
+
+# Mobile
+
+[](http://www.youtube.com/watch?v=oGMsSKyh6tc "Supabase & Keyri | Mobile Integration Overview")
+
+### Install Flutter
+
+First, install the Flutter SDK, found at flutter.dev
+
+Make sure to add Flutter to your PATH, for example:
+
+```shell
+export PATH="$PATH:`pwd`/flutter/bin"
+```
+
+### Apple - initial setup
+
+Download the latest version of Xcode from the Mac App Store. Make sure the Xcode provided simulator is using a 64-bit device (iPhone 5s or later). You can check the device by viewing the settings in the simulator’s **Hardware > Device** or **File > Open Simulator** menus.
+
+### Android - initial setup
+
+Download the latest version of [Android Studio](https://developer.android.com/studio). Install Android SDK and needed emulator(s).
+
+### Create Project
+
+Run this command in your terminal/shell at the desired location for your new project
+
+```shell
+$ flutter create my_app
+```
+
+You can then CD into the new directory, and run the test app with
+
+```shell
+flutter run
+```
+
+This is a good test - if things are configured correctly so far you should see the default Flutter test app deployed.
+
+### Add dependencies (Keyri and Supabase)
+
+Open your Pubspec.yaml file, which should be at the top level directory in your new project
+
+Add Keyri and Supabase under **dependencies**
+
+
+
+One can now access Supabase and Keyri sdks in their Flutter code
+
+### Utilize the two together
+
+1. Make a request to Supabase to authenticate the user
+
+2. Parse the response to extract the token
+
+3. Authenticate using Keyri
+ 1. Below, we show how to utilize the EasyKeyriAuth function, which takes the user through scanning the code, creating the session, displaying the confirmation screen, and finalizing the payload transmission
+ - Note - you can find your App Key in the Keyri Developer Portal
+
+ 2. Alternatively, intermediate functions in the Keyri SDK, discussed in the mobile docs, can provide control over displaying a custom QR Scanner and/or Confirmation screen
+
+```kotlin
+// Sign in user with email and password
+// Alternatively one can utilize the Supabase API to accomplish the same thing
+final response = await client.auth.signIn(email: 'email', password: 'password');
+
+if (response.error != null) {
+ // Error
+ print('Error: ${response.error?.message}');
+} else {
+ // Success
+ final session = response.data;
+
+ // This is the payload that needs to be send through Keyri
+ final refreshToken = session.refreshToken
+
+ // EasyKeyriAuth guides the user through scanning and parsing the QR, confirming the session, and configuring the payload
+ // One can also use the initiateQRSession method to use the Keyri Scanner with a custom Confirmation screen
+ // Or the ProcessLink method if you have your own scanner or are using deep linking
+ await keyri
+ .easyKeyriAuth([App Key],
+ '{"refreshToken":"$refreshToken"}', [email])
+ .then((authResult) => _onAuthResult(authResult))
+ .catchError((error, stackTrace) => _onError(error));
+
+}
+
+
+```
diff --git a/apps/reference/docs/guides/realtime/quickstart.mdx b/apps/reference/docs/guides/realtime/quickstart.mdx
index f1918fe9ab6..47a77610d94 100644
--- a/apps/reference/docs/guides/realtime/quickstart.mdx
+++ b/apps/reference/docs/guides/realtime/quickstart.mdx
@@ -103,7 +103,7 @@ const channel = supabase.channel('calc-latency', {
})
channel.subscribe(async (status) => {
- if (status === 'SUBSCRIBED) {
+ if (status === 'SUBSCRIBED') {
const begin = performance.now()
await channel.send({
diff --git a/apps/reference/docs/guides/with-nextjs.mdx b/apps/reference/docs/guides/with-nextjs.mdx
index ebcc253325c..3d40b368b08 100644
--- a/apps/reference/docs/guides/with-nextjs.mdx
+++ b/apps/reference/docs/guides/with-nextjs.mdx
@@ -61,6 +61,7 @@ Now we are going to set up the database schema. We can use the "User Management
or you can just copy/paste the SQL from below and run it yourself.
-
+
+Wrap your `pages/_app.tsx` component with the `SessionContextProvider` component:
+
+```jsx title="pages/_app.tsx"
+import { createBrowserSupabaseClient } from '@supabase/auth-helpers-nextjs'
+// highlight-next-line
+import { SessionContextProvider, Session } from '@supabase/auth-helpers-react'
+
+function MyApp({
+ Component,
+ pageProps,
+}: AppProps<{
+ // highlight-next-line
+ initialSession: Session,
+}>) {
+ const [supabaseClient] = useState(() => createBrowserSupabaseClient())
+
+ return (
+
+
+ )
+}
+```
+
+See the [Auth Helpers docs](/docs/guides/auth/auth-helpers/nextjs#usage-with-typescript) for more details on usage with TypeScript.
+
+
+
+
+#### Supabase Auth UI
+
+We can use the [Supabase Auth UI](https://supabase.com/docs/guides/auth/auth-helpers/auth-ui) a pre-built React component for authenticating users via OAuth, email, and magic links.
+
+Install the Supabase Auth UI for React
+
+```bash
+npm install @supabase/auth-ui-react
+```
+
+Add the `Auth` component to your home page
+
+```jsx title="pages/index.js"
+import type { NextPage } from 'next'
+import { Auth, ThemeSupa } from '@supabase/auth-ui-react'
+import { useSession, useSupabaseClient } from '@supabase/auth-helpers-react'
+
+const Home: NextPage = () => {
+ const session = useSession()
+ const supabase = useSupabaseClient()
+
+ return (
+
+
-```jsx title="components/Account.js"
+Let's create a new component for that called `Account.js` within a `components` folder.
+
+```tsx title="components/Account.js"
import { useState, useEffect } from 'react'
-import { supabase } from '../utils/supabaseClient'
+import { useUser, useSupabaseClient } from '@supabase/auth-helpers-react'
export default function Account({ session }) {
+ const supabase = useSupabaseClient()
+ const user = useUser()
const [loading, setLoading] = useState(true)
const [username, setUsername] = useState(null)
const [website, setWebsite] = useState(null)
@@ -278,27 +362,9 @@ export default function Account({ session }) {
getProfile()
}, [session])
- async function getCurrentUser() {
- const {
- data: { session },
- error,
- } = await supabase.auth.getSession()
-
- if (error) {
- throw error
- }
-
- if (!session?.user) {
- throw new Error('User not logged in')
- }
-
- return session.user
- }
-
async function getProfile() {
try {
setLoading(true)
- const user = await getCurrentUser()
let { data, error, status } = await supabase
.from('profiles')
@@ -316,7 +382,8 @@ export default function Account({ session }) {
setAvatarUrl(data.avatar_url)
}
} catch (error) {
- alert(error.message)
+ alert('Error loading user data!')
+ console.log(error)
} finally {
setLoading(false)
}
@@ -325,23 +392,21 @@ export default function Account({ session }) {
async function updateProfile({ username, website, avatar_url }) {
try {
setLoading(true)
- const user = await getCurrentUser()
const updates = {
id: user.id,
username,
website,
avatar_url,
- updated_at: new Date(),
+ updated_at: new Date().toISOString(),
}
let { error } = await supabase.from('profiles').upsert(updates)
-
- if (error) {
- throw error
- }
+ if (error) throw error
+ alert('Profile updated!')
} catch (error) {
- alert(error.message)
+ alert('Error updating the data!')
+ console.log(error)
} finally {
setLoading(false)
}
@@ -354,7 +419,7 @@ export default function Account({ session }) {
-
+ Supabase + Next.js
-- Sign in via magic link with your email below -
-
- setEmail(e.target.value)}
- />
-
-
-
-
-
+ {!session ? (
+
)
}
+
+export default Home
```
### Account page
After a user is signed in we can allow them to edit their profile details and manage their account.
-Let's create a new component for that called `Account.js`.
+Account page will go here.
+ )}
-
+
+
+
+Let's create a new component for that called `Account.tsx` within a `components` folder.
+
+```tsx title="components/Account.tsx"
+import { useState, useEffect } from 'react'
+import {
+ useUser,
+ useSupabaseClient,
+ Session,
+} from '@supabase/auth-helpers-react'
+import { Database } from '../utils/database.types'
+type Profiles = Database['public']['Tables']['profiles']['Row']
+
+export default function Account({ session }: { session: Session }) {
+ const supabase = useSupabaseClient()
+ const user = useUser()
+ const [loading, setLoading] = useState(true)
+ const [username, setUsername] = useState(null)
+ const [website, setWebsite] = useState(null)
+ const [avatar_url, setAvatarUrl] = useState(null)
+
+ useEffect(() => {
+ getProfile()
+ }, [session])
+
+ async function getProfile() {
+ try {
+ setLoading(true)
+ if (!user) throw new Error('No user')
+
+ let { data, error, status } = await supabase
+ .from('profiles')
+ .select(`username, website, avatar_url`)
+ .eq('id', user.id)
+ .single()
+
+ if (error && status !== 406) {
+ throw error
+ }
+
+ if (data) {
+ setUsername(data.username)
+ setWebsite(data.website)
+ setAvatarUrl(data.avatar_url)
+ }
+ } catch (error) {
+ alert('Error loading user data!')
+ console.log(error)
+ } finally {
+ setLoading(false)
+ }
+ }
+
+ async function updateProfile({
+ username,
+ website,
+ avatar_url,
+ }: {
+ username: Profiles['username']
+ website: Profiles['website']
+ avatar_url: Profiles['avatar_url']
+ }) {
+ try {
+ setLoading(true)
+ if (!user) throw new Error('No user')
+
+ const updates = {
+ id: user.id,
+ username,
+ website,
+ avatar_url,
+ updated_at: new Date().toISOString(),
+ }
+
+ let { error } = await supabase.from('profiles').upsert(updates)
+ if (error) throw error
+ alert('Profile updated!')
+ } catch (error) {
+ alert('Error updating the data!')
+ console.log(error)
+ } finally {
+ setLoading(false)
+ }
+ }
+
+ return (
+
+
+
### Launch!
Now that we have all the components in place, let's update `pages/index.js`:
```jsx title="pages/index.js"
-import { useState, useEffect } from 'react'
-import { supabase } from '../utils/supabaseClient'
-import Auth from '../components/Auth'
+import type { NextPage } from 'next'
+import { Auth, ThemeSupa } from '@supabase/auth-ui-react'
+import { useSession, useSupabaseClient } from '@supabase/auth-helpers-react'
+// highlight-next-line
import Account from '../components/Account'
-export default function Home() {
- const [isLoading, setIsLoading] = useState(true)
- const [session, setSession] = useState(null)
-
- useEffect(() => {
- let mounted = true
-
- async function getInitialSession() {
- const {
- data: { session },
- } = await supabase.auth.getSession()
-
- // only update the react state if the component is still mounted
- if (mounted) {
- if (session) {
- setSession(session)
- }
-
- setIsLoading(false)
- }
- }
-
- getInitialSession()
-
- const { subscription } = supabase.auth.onAuthStateChange(
- (_event, session) => {
- setSession(session)
- }
- )
-
- return () => {
- mounted = false
-
- subscription?.unsubscribe()
- }
- }, [])
+const Home: NextPage = () => {
+ const session = useSession()
+ const supabase = useSupabaseClient()
return (
+
```jsx title="components/Avatar.js"
-import { useEffect, useState } from 'react'
-import { supabase } from '../utils/supabaseClient'
+import React, { useEffect, useState } from 'react'
+import { useSupabaseClient } from '@supabase/auth-helpers-react'
-export default function Avatar({ url, size, onUpload }) {
+export default function Avatar({ uid, url, size, onUpload }) {
+ const supabase = useSupabaseClient()
const [avatarUrl, setAvatarUrl] = useState(null)
const [uploading, setUploading] = useState(false)
@@ -497,11 +682,11 @@ export default function Avatar({ url, size, onUpload }) {
const url = URL.createObjectURL(data)
setAvatarUrl(url)
} catch (error) {
- console.log('Error downloading image: ', error.message)
+ console.log('Error downloading image: ', error)
}
}
- async function uploadAvatar(event) {
+ const uploadAvatar = async (event) => {
try {
setUploading(true)
@@ -511,12 +696,12 @@ export default function Avatar({ url, size, onUpload }) {
const file = event.target.files[0]
const fileExt = file.name.split('.').pop()
- const fileName = `${Math.random()}.${fileExt}`
+ const fileName = `${uid}.${fileExt}`
const filePath = `${fileName}`
let { error: uploadError } = await supabase.storage
.from('avatars')
- .upload(filePath, file)
+ .upload(filePath, file, { upsert: true })
if (uploadError) {
throw uploadError
@@ -524,7 +709,8 @@ export default function Avatar({ url, size, onUpload }) {
onUpload(filePath)
} catch (error) {
- alert(error.message)
+ alert('Error uploading avatar!')
+ console.log(error)
} finally {
setUploading(false)
}
@@ -566,6 +752,120 @@ export default function Avatar({ url, size, onUpload }) {
}
```
+
+
+
+```tsx title="components/Avatar.tsx"
+import React, { useEffect, useState } from 'react'
+import { useSupabaseClient } from '@supabase/auth-helpers-react'
+import { Database } from '../utils/database.types'
+type Profiles = Database['public']['Tables']['profiles']['Row']
+
+export default function Avatar({
+ uid,
+ url,
+ size,
+ onUpload,
+}: {
+ uid: string
+ url: Profiles['avatar_url']
+ size: number
+ onUpload: (url: string) => void
+}) {
+ const supabase = useSupabaseClient()
+ const [avatarUrl, setAvatarUrl] = useState(null)
+ const [uploading, setUploading] = useState(false)
+
+ useEffect(() => {
+ if (url) downloadImage(url)
+ }, [url])
+
+ async function downloadImage(path: string) {
+ try {
+ const { data, error } = await supabase.storage
+ .from('avatars')
+ .download(path)
+ if (error) {
+ throw error
+ }
+ const url = URL.createObjectURL(data)
+ setAvatarUrl(url)
+ } catch (error) {
+ console.log('Error downloading image: ', error)
+ }
+ }
+
+ const uploadAvatar: React.ChangeEventHandler = async (
+ event
+ ) => {
+ try {
+ setUploading(true)
+
+ if (!event.target.files || event.target.files.length === 0) {
+ throw new Error('You must select an image to upload.')
+ }
+
+ const file = event.target.files[0]
+ const fileExt = file.name.split('.').pop()
+ const fileName = `${uid}.${fileExt}`
+ const filePath = `${fileName}`
+
+ let { error: uploadError } = await supabase.storage
+ .from('avatars')
+ .upload(filePath, file, { upsert: true })
+
+ if (uploadError) {
+ throw uploadError
+ }
+
+ onUpload(filePath)
+ } catch (error) {
+ alert('Error uploading avatar!')
+ console.log(error)
+ } finally {
+ setUploading(false)
+ }
+ }
+
+ return (
+
+
+
### Add the new widget
And then we can add the widget to the Account page:
@@ -580,6 +880,7 @@ return (
)
diff --git a/apps/www/lib/redirects.js b/apps/www/lib/redirects.js
index 97e6e3bfc04..bed6e889a50 100644
--- a/apps/www/lib/redirects.js
+++ b/apps/www/lib/redirects.js
@@ -270,7 +270,7 @@ module.exports = [
{
permanent: false,
source: '/docs/client/auth-session',
- destination: '/docs/reference/javascript/auth-session',
+ destination: '/docs/reference/javascript/v1/auth-session',
},
{
permanent: false,
@@ -325,12 +325,12 @@ module.exports = [
{
permanent: false,
source: '/docs/client/removesubscription',
- destination: '/docs/reference/javascript/removesubscription',
+ destination: '/docs/reference/javascript/v1/removesubscription',
},
{
permanent: false,
source: '/docs/client/getsubscriptions',
- destination: '/docs/reference/javascript/getsubscriptions',
+ destination: '/docs/reference/javascript/v1/getsubscriptions',
},
{
permanent: false,
@@ -1359,60 +1359,120 @@ module.exports = [
destination: '/docs/guides/auth/auth-helpers/sveltekit',
},
- // V2 redirects
- // {
- // permanent: true,
- // source: '/docs/reference/javascript/auth-update',
- // destination: '/docs/reference/javascript/auth-updateuser',
- // },
- // {
- // permanent: true,
- // source: '/docs/reference/javascript/auth-api-getuser',
- // destination: '/docs/reference/javascript/auth-getuser',
- // },
- // {
- // permanent: true,
- // source: '/docs/reference/javascript/auth-api-resetpasswordforemail',
- // destination: '/docs/reference/javascript/auth-resetpasswordforemail',
- // },
- // {
- // permanent: true,
- // source: '/docs/reference/javascript/auth-api-verifyotp',
- // destination: '/docs/reference/javascript/auth-verifyotp',
- // },
- // {
- // permanent: true,
- // source: '/docs/reference/javascript/auth-api-listusers',
- // destination: '/docs/reference/javascript/auth-admin-listusers',
- // },
- // {
- // permanent: true,
- // source: '/docs/reference/javascript/auth-api-createuser',
- // destination: '/docs/reference/javascript/auth-admin-createuser',
- // },
- // {
- // permanent: true,
- // source: '/docs/reference/javascript/auth-api-deleteuser',
- // destination: '/docs/reference/javascript/auth-admin-deleteuser',
- // },
- // {
- // permanent: true,
- // source: '/docs/reference/javascript/auth-api-generatelink',
- // destination: '/docs/reference/javascript/auth-admin-generatelink',
- // },
- // {
- // permanent: true,
- // source: '/docs/reference/javascript/auth-api-inviteuserbyemail',
- // destination: '/docs/reference/javascript/auth-admin-inviteuserbyemail',
- // },
- // {
- // permanent: true,
- // source: '/docs/reference/javascript/auth-api-getuserbyid',
- // destination: '/docs/reference/javascript/auth-admin-getuserbyid',
- // },
- // {
- // permanent: true,
- // source: '/docs/reference/javascript/auth-api-updateuserbyid',
- // destination: '/docs/reference/javascript/auth-admin-updateuserbyid',
- // },
+ // supabase-js v1 to v2 redirects
+ // v1: /auth-update
+ // v2: /auth-updateuser
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/auth-update',
+ destination: '/docs/reference/javascript/v1/auth-update',
+ },
+ // v1: /auth-api-get-user
+ // v2: /auth-getuser
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/auth-api-getuser',
+ destination: '/docs/reference/javascript/v1/auth-api-getuser',
+ },
+ // v1: /auth-api-resetpasswordforemail
+ // v2: /auth-resetpasswordforemail
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/auth-api-resetpasswordforemail',
+ destination: '/docs/reference/javascript/v1/auth-api-resetpasswordforemail',
+ },
+ // v1: /auth-api-verifyotp
+ // v2: /auth-verifyotp
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/auth-api-verifyotp',
+ destination: '/docs/reference/javascript/v1/auth-api-verifyotp',
+ },
+ // v1: /auth-api-listusers
+ // v2: /auth-admin-listusers
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/auth-api-listusers',
+ destination: '/docs/reference/javascript/v1/auth-api-listusers',
+ },
+ // v1: /auth-api-createuser
+ // v2: /auth-admin-createuser
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/auth-api-createuser',
+ destination: '/docs/reference/javascript/v1/auth-api-createuser',
+ },
+ // v1: /auth-api-deleteuser
+ // v2: /auth-admin-deleteuser
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/auth-api-deleteuser',
+ destination: '/docs/reference/javascript/v1/auth-api-deleteuser',
+ },
+ // v1: /auth-api-generatelink
+ // v2: /auth-admin-generatelink
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/auth-api-generatelink',
+ destination: '/docs/reference/javascript/v1/auth-api-generatelink',
+ },
+ // v1: /auth-api-inviteuserbyemail
+ // v2: /auth-admin-inviteuserbyemail
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/auth-api-inviteuserbyemail',
+ destination: '/docs/reference/javascript/v1/auth-api-inviteuserbyemail',
+ },
+ // v1: /auth-api-getuserbyid
+ // v2: /auth-admin-getuserbyid
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/auth-api-getuserbyid',
+ destination: '/docs/reference/javascript/v1/auth-api-getuserbyid',
+ },
+ // v1: /auth-api-updateuserbyid
+ // v2: /auth-admin-updateuserbyid
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/auth-api-updateuserbyid',
+ destination: '/docs/reference/javascript/v1/auth-api-updateuserbyid',
+ },
+ // signIn method is now split into signInWithPassword ,signInWithPasswordless ,signInWithOAuth
+ // send traffic to v1 docs instead
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/auth-signin',
+ destination: '/docs/reference/javascript/v1/auth-signin',
+ },
+ // v1: /auth-session
+ // v2: /auth-getsession
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/auth-session',
+ destination: '/docs/reference/javascript/v1/auth-session',
+ },
+ // v1: /auth-api-sendmobileotp
+ // v2: /auth-signinwithotp
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/auth-api-sendmobileotp',
+ destination: '/docs/reference/javascript/v1/auth-api-sendmobileotp',
+ },
+
+ // realtime methods been replaced with new names
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/removesubscription',
+ destination: '/docs/reference/javascript/v1/removesubscription',
+ },
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/removeallsubscriptions',
+ destination: '/docs/reference/javascript/v1/removeallsubscriptions',
+ },
+ {
+ permanent: true,
+ source: '/docs/reference/javascript/getsubscriptions',
+ destination: '/docs/reference/javascript/v1/getsubscriptions',
+ },
]
diff --git a/apps/www/pages/legal/dpa.tsx b/apps/www/pages/legal/dpa.tsx
index ad9ecd2b3d4..0cb1cc54d2d 100644
--- a/apps/www/pages/legal/dpa.tsx
+++ b/apps/www/pages/legal/dpa.tsx
@@ -49,11 +49,7 @@ const DPA = () => {
("DPA").
-
+
+ )
+}
+```
+
+
+
+
+
+
+
+ setUsername(e.target.value)}
+ />
+
+
+
+ setWebsite(e.target.value)}
+ />
+
+
+
+
+
+
+
+
+
+
{!session ? (
-
)
}
+
+export default Home
```
Once that's done, run this in a terminal window:
@@ -462,8 +640,6 @@ npm run dev
And then open the browser to [localhost:3000](http://localhost:3000) and you should see the completed app.
-
-
## Bonus: Profile photos
Every Supabase project is configured with [Storage](/docs/guides/storage) for managing large files like
@@ -471,14 +647,23 @@ photos and videos.
### Create an upload widget
-Let's create an avatar for the user so that they can upload a profile photo.
-We can start by creating a new component:
+Let's create an avatar widget for the user so that they can upload a profile photo. We can start by creating a new component:
+
+
+ {avatarUrl ? (
+ 
+ ) : (
+
+ )}
+
+ )
+}
+```
+
+
+
+
+
+
{/* Add to the body */}
{
@@ -596,5 +897,8 @@ return (
At this stage you have a fully functional application!
+- See the complete [example on GitHub](https://github.com/supabase/supabase/tree/master/examples/user-management/nextjs-ts-user-management) and deploy it to Vercel.
+- Explore the [Auth Helpers for Next.js](https://supabase.com/docs/guides/auth/auth-helpers/nextjs).
+- Explore the [pre-built Auth UI for React](https://supabase.com/docs/guides/auth/auth-helpers/auth-ui).
- Got a question? [Ask here](https://github.com/supabase/supabase/discussions).
- Sign in: [app.supabase.com](https://app.supabase.com)
diff --git a/apps/reference/docs/guides/with-solidjs.mdx b/apps/reference/docs/guides/with-solidjs.mdx
index da23c294236..e601c98aee8 100644
--- a/apps/reference/docs/guides/with-solidjs.mdx
+++ b/apps/reference/docs/guides/with-solidjs.mdx
@@ -271,9 +271,9 @@ interface Props {
const Account: Component = ({ session }) => {
const [loading, setLoading] = createSignal(true)
- const [username, setUsername] = (createSignal < string) | (null > null)
- const [website, setWebsite] = (createSignal < string) | (null > null)
- const [avatarUrl, setAvatarUrl] = (createSignal < string) | (null > null)
+ const [username, setUsername] = createSignal(null)
+ const [website, setWebsite] = createSignal(null)
+ const [avatarUrl, setAvatarUrl] = createSignal(null)
createEffect(() => {
getProfile()
diff --git a/apps/reference/docs/guides/with-vue-3.mdx b/apps/reference/docs/guides/with-vue-3.mdx
index 06b7f9e0617..49ce6b3739b 100644
--- a/apps/reference/docs/guides/with-vue-3.mdx
+++ b/apps/reference/docs/guides/with-vue-3.mdx
@@ -24,7 +24,7 @@ By the end of this guide you'll have an app which allows users to login and upda
### GitHub
-Whenever you get stuck at any point, take a look at [this repo](https://github.com/zernonia/supabase-vue-3).
+Whenever you get stuck at any point, take a look at [this repo](https://github.com/supabase/examples/tree/main/supabase-js-v2/user-management/vue3-user-management).
## Project set up
@@ -182,102 +182,141 @@ const supabaseAnonKey = import.meta.env.VITE_SUPABASE_ANON_KEY
export const supabase = createClient(supabaseUrl, supabaseAnonKey)
```
-And one optional step is to update the CSS file `src/assets/main.css` to make the app look nice.
-You can find the full contents of this file [here](https://raw.githubusercontent.com/supabase/examples/main/supabase-js-v2/user-management/react-user-management/src/index.css).
-
-```javascript title="src/main.js"
-import { createApp } from 'vue'
-import App from './App.vue'
-import './assets/main.css'
-
-createApp(App).mount('#app')
-```
+Optionally, update [src/style.css](https://raw.githubusercontent.com/supabase/examples/main/supabase-js-v2/user-management/vue3-user-management/src/style.css) to style the app.
### Set up a Login component
Let's set up a Vue component to manage logins and sign ups. We'll use Magic Links, so users can sign in with their email without using passwords.
```html title="/src/components/Auth.vue"
+
+
-
-
-```
-
-### User store
-
-To access the user information in other places, we use a reactive store. Create a new file called `store.js` and utilize Vue 3 `reactive` functionalities.
-
-```javascript title="src/store.js"
-import { reactive } from 'vue'
-
-export const store = reactive({
- user: {},
-})
```
### Account page
After a user is signed in we can allow them to edit their profile details and manage their account.
-Let's create a new component for that called `Profile.vue`.
+Let's create a new component for that called `Account.vue`.
+
+```html title="src/components/Account.vue"
+
-```html title="src/components/Profile.vue"
-
-
```
### Launch!
@@ -403,37 +346,31 @@ Let's create a new component for that called `Profile.vue`.
Now that we have all the components in place, let's update `App.vue`:
```html title="src/App.vue"
+
+
-
-
-
-
```
Once that's done, run this in a terminal window:
@@ -442,7 +379,7 @@ Once that's done, run this in a terminal window:
npm run dev
```
-And then open the browser to [localhost:3000](http://localhost:3000) and you should see the completed app.
+And then open the browser to [localhost:5173](http://localhost:5173) and you should see the completed app.
@@ -455,132 +392,96 @@ Every Supabase project is configured with [Storage](/docs/guides/storage) for ma
Let's create an avatar for the user so that they can upload a profile photo. We can start by creating a new component:
```html title="src/components/Avatar.vue"
+
+
- ![Avatar]()
-
+ ![Avatar]()
+
-
+
-
-
```
### Add the new widget
And then we can add the widget to the Account page:
-```html title="src/Profile.vue"
+```html title="src/components/Account.vue"
+
+
-
-
```
## Next steps
diff --git a/apps/reference/docusaurus.config.js b/apps/reference/docusaurus.config.js
index ba1093b6fb0..56e2df43582 100644
--- a/apps/reference/docusaurus.config.js
+++ b/apps/reference/docusaurus.config.js
@@ -14,7 +14,7 @@ const config = {
url: 'https://supabase.com',
baseUrl: baseUrl,
onBrokenLinks: 'throw',
- onBrokenMarkdownLinks: 'warn',
+ onBrokenMarkdownLinks: 'throw',
favicon: '/favicon.ico',
themes: ['docusaurus-theme-search-typesense'],
diff --git a/apps/reference/nav/_referenceSidebars.js b/apps/reference/nav/_referenceSidebars.js
index e0150208708..dc9252ce16b 100644
--- a/apps/reference/nav/_referenceSidebars.js
+++ b/apps/reference/nav/_referenceSidebars.js
@@ -4,7 +4,7 @@ const sidebars = {
type: 'category',
label: 'Overview',
collapsed: true,
- items: ['about', 'architecture', 'guides/examples'],
+ items: ['about', 'guides/features', 'architecture', 'guides/examples'],
},
{
type: 'category',
@@ -80,6 +80,7 @@ const sidebars = {
'guides/auth/row-level-security',
'guides/auth/managing-user-data',
'guides/auth/auth-captcha',
+ 'guides/auth/server-side-rendering',
],
},
{
@@ -215,22 +216,51 @@ const sidebars = {
label: 'Integrations',
collapsed: true,
items: [
- 'guides/integrations/appsmith',
- 'guides/integrations/auth0',
- 'guides/integrations/authsignal',
- 'guides/integrations/clerk',
- 'guides/integrations/dashibase',
- 'guides/integrations/directus',
- 'guides/integrations/draftbit',
- 'guides/integrations/pgmustard',
- 'guides/integrations/plasmic',
- 'guides/integrations/polyscale',
- 'guides/integrations/prisma',
- 'guides/integrations/sequin',
- 'guides/integrations/snaplet',
- 'guides/integrations/stytch',
- 'guides/integrations/supertokens',
- 'guides/integrations/vercel',
+ 'guides/integrations/integrations',
+ {
+ type: 'category',
+ label: 'Auth',
+ collapsed: true,
+ items: [
+ 'guides/integrations/auth0',
+ 'guides/integrations/authsignal',
+ 'guides/integrations/clerk',
+ 'guides/integrations/keyri',
+ 'guides/integrations/stytch',
+ 'guides/integrations/supertokens',
+ ],
+ },
+ {
+ type: 'category',
+ label: 'Caching / Offline-first',
+ collapsed: true,
+ items: ['guides/integrations/polyscale'],
+ },
+ {
+ type: 'category',
+ label: 'Developer Tools',
+ collapsed: true,
+ items: [
+ 'guides/integrations/pgmustard',
+ 'guides/integrations/prisma',
+ 'guides/integrations/sequin',
+ 'guides/integrations/snaplet',
+ 'guides/integrations/vercel',
+ ],
+ },
+ {
+ type: 'category',
+ label: 'Low-code',
+ collapsed: true,
+ items: [
+ 'guides/integrations/appsmith',
+ 'guides/integrations/dashibase',
+ 'guides/integrations/dhiwise',
+ 'guides/integrations/directus',
+ 'guides/integrations/draftbit',
+ 'guides/integrations/plasmic',
+ ],
+ },
],
},
],
diff --git a/apps/reference/static/img/guides/integrations/dhiwise/auth.gif b/apps/reference/static/img/guides/integrations/dhiwise/auth.gif
new file mode 100644
index 00000000000..db05bb42fca
Binary files /dev/null and b/apps/reference/static/img/guides/integrations/dhiwise/auth.gif differ
diff --git a/apps/reference/static/img/guides/integrations/dhiwise/authKeys.png b/apps/reference/static/img/guides/integrations/dhiwise/authKeys.png
new file mode 100644
index 00000000000..1ac402f5d9b
Binary files /dev/null and b/apps/reference/static/img/guides/integrations/dhiwise/authKeys.png differ
diff --git a/apps/reference/static/img/guides/integrations/dhiwise/create.png b/apps/reference/static/img/guides/integrations/dhiwise/create.png
new file mode 100644
index 00000000000..bcb06e5e5ee
Binary files /dev/null and b/apps/reference/static/img/guides/integrations/dhiwise/create.png differ
diff --git a/apps/reference/static/img/guides/integrations/dhiwise/newProj.png b/apps/reference/static/img/guides/integrations/dhiwise/newProj.png
new file mode 100644
index 00000000000..e3f5d8db355
Binary files /dev/null and b/apps/reference/static/img/guides/integrations/dhiwise/newProj.png differ
diff --git a/apps/reference/static/img/guides/integrations/dhiwise/select.png b/apps/reference/static/img/guides/integrations/dhiwise/select.png
new file mode 100644
index 00000000000..3de535da47e
Binary files /dev/null and b/apps/reference/static/img/guides/integrations/dhiwise/select.png differ
diff --git a/apps/www/README.md b/apps/www/README.md
index ab4de38784c..5505fe5a8a0 100644
--- a/apps/www/README.md
+++ b/apps/www/README.md
@@ -16,7 +16,6 @@ cd supabase
npm install
npm run dev
-
# visit website
http://localhost:3000
```
diff --git a/apps/www/_blog/2022-10-14-postgres-full-text-search-vs-the-rest.mdx b/apps/www/_blog/2022-10-14-postgres-full-text-search-vs-the-rest.mdx
index d14a3b671cb..f96545c783a 100644
--- a/apps/www/_blog/2022-10-14-postgres-full-text-search-vs-the-rest.mdx
+++ b/apps/www/_blog/2022-10-14-postgres-full-text-search-vs-the-rest.mdx
@@ -206,7 +206,7 @@ We'll focus on the end-user-centric meaning of performance here (query speed).
Postgres is capable of loading CSVs, but since we'll be using other search engines as well, let's convert to format that's much easier to use and process - [Newline Delimited JSON](https://dataprotocols.org/ndjson/).
-After a few lines of code and one `[csv2ndjson.mjs` script](https://github.com/VADOSWARE/fts-benchmark/blob/main/src/util/csv2ndjson.mjs) later, we have a `movies.ndjson.json` full of JSON documents that we can easily ingest into any search engine (or other database for that matter!).
+After a few lines of code and one [`csv2ndjson.mjs` script](https://github.com/VADOSWARE/fts-benchmark/blob/main/src/util/csv2ndjson.mjs) later, we have a `movies.ndjson.json` full of JSON documents that we can easily ingest into any search engine (or other database for that matter!).
### Inserting the data
diff --git a/apps/www/components/CaseStudies/benchmark.tsx b/apps/www/components/CaseStudies/benchmark.tsx
index 630e7b6e7cf..1e2a218bf1a 100644
--- a/apps/www/components/CaseStudies/benchmark.tsx
+++ b/apps/www/components/CaseStudies/benchmark.tsx
@@ -31,11 +31,6 @@ const Benchmark = () => {
-
+
-
-
-
-
- You can download the latest DPA document through our{' '} - security portal, or by - submitting your email here. -
+You can download our latest DPA document by submitting your email here.
{formSubmitted ? (diff --git a/apps/www/pages/legal/soc2.tsx b/apps/www/pages/legal/soc2.tsx index c58ebe4dfef..f5fc2a80fac 100644 --- a/apps/www/pages/legal/soc2.tsx +++ b/apps/www/pages/legal/soc2.tsx @@ -18,11 +18,7 @@ const SOC2 = () => { getting certified for SOC2 Type 2 and HIPAA next.
-- You can request for our latest SOC 2 document either through our{' '} - security portal, or by submitting - your request here. -
+You can request for our latest SOC 2 document by submitting your request here.
@@ -126,8 +126,7 @@ In addition to internal security reviews, we use various tools to scan our code