style: use GitHub's right product name (#38099)
* style: use GitHub's right product name * fix: use correct kotlin provider
This commit is contained in:
Raúl Barroso
GitHub
@@ -203,7 +203,7 @@ Some things to consider:
|
||||
|
||||
## Community channels
|
||||
|
||||
If you get stuck somewhere or have any questions, join our [Discord Community Server](https://discord.supabase.com/) or the [Github Discussions](https://github.com/supabase/supabase/discussions). We are here to help!
|
||||
If you get stuck somewhere or have any questions, join our [Discord Community Server](https://discord.supabase.com/) or the [GitHub Discussions](https://github.com/supabase/supabase/discussions). We are here to help!
|
||||
|
||||
## Contributors
|
||||
|
||||
|
||||
@@ -102,7 +102,7 @@ With Deep Linking, you can configure this redirect to open a specific page. This
|
||||
|
||||
return (
|
||||
<>
|
||||
<Button onPress={performOAuth} title="Sign in with Github" />
|
||||
<Button onPress={performOAuth} title="Sign in with GitHub" />
|
||||
<Button onPress={sendMagicLink} title="Send Magic Link" />
|
||||
</>
|
||||
);
|
||||
|
||||
@@ -119,7 +119,7 @@ func signInWithGithub() async throws {
|
||||
</TabPanel>
|
||||
<TabPanel id="kotlin" label="Kotlin">
|
||||
|
||||
When your user signs in, call [signInWith(Provider)](/docs/reference/kotlin/auth-signinwithoauth) with `Github` as the `Provider`:
|
||||
When your user signs in, call [signInWith(Provider)](/docs/reference/kotlin/auth-signinwithoauth) with [`Github`](https://github.com/supabase-community/supabase-kt/blob/master/Auth/src/commonMain/kotlin/io/github/jan/supabase/auth/providers/Providers.kt#L16-L20) as the `Provider`:
|
||||
|
||||
```kotlin
|
||||
suspend fun signInWithGithub() {
|
||||
|
||||
@@ -94,7 +94,7 @@ Check out the [Edge Function Examples](https://github.com/supabase/supabase/tree
|
||||
href: '/guides/functions/connect-to-postgres',
|
||||
},
|
||||
{
|
||||
name: 'Github Actions',
|
||||
name: 'GitHub Actions',
|
||||
description: `Deploying Edge Functions with GitHub Actions.`,
|
||||
href: '/guides/functions/examples/github-actions',
|
||||
},
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title = "Converted Github account to organization - Lost Supabase account access"
|
||||
title = "Converted GitHub account to organization - Lost Supabase account access"
|
||||
github_url = "https://github.com/orgs/supabase/discussions/21101"
|
||||
date_created = "2024-02-08T01:39:25+00:00"
|
||||
topics = [ "auth" ]
|
||||
|
||||
@@ -3125,7 +3125,7 @@ functions:
|
||||
- name: provider
|
||||
isOptional: false
|
||||
type: OAuthProvider
|
||||
description: The OAuth provider to use for the user's authentication, for example `Google` or `Github`.
|
||||
description: The OAuth provider to use for the user's authentication, for example `Google` or `GitHub`.
|
||||
- name: redirectUrl
|
||||
isOptional: true
|
||||
type: String?
|
||||
|
||||
@@ -3192,7 +3192,7 @@ functions:
|
||||
- name: provider
|
||||
isOptional: false
|
||||
type: OAuthProvider
|
||||
description: The OAuth provider to use for the user's authentication, for example `Google` or `Github`.
|
||||
description: The OAuth provider to use for the user's authentication, for example `Google` or `GitHub`.
|
||||
- name: redirectUrl
|
||||
isOptional: true
|
||||
type: String?
|
||||
|
||||
@@ -129,7 +129,7 @@ const FeaturePreviewModal = () => {
|
||||
<div className="mt-1 mb-3 flex flex-col items-center gap-y-0.5">
|
||||
<p className="text-sm">No feature previews available</p>
|
||||
<p className="text-sm text-foreground-light">
|
||||
Have an idea for the dashboard? Let us know via Github Discussions!
|
||||
Have an idea for the dashboard? Let us know via GitHub Discussions!
|
||||
</p>
|
||||
</div>
|
||||
<Button asChild type="default" icon={<ExternalLink strokeWidth={1.5} />}>
|
||||
@@ -138,7 +138,7 @@ const FeaturePreviewModal = () => {
|
||||
target="_blank"
|
||||
rel="noreferrer"
|
||||
>
|
||||
Github Discussions
|
||||
GitHub Discussions
|
||||
</Link>
|
||||
</Button>
|
||||
</div>
|
||||
|
||||
@@ -66,7 +66,7 @@ const IntegrationSettings = () => {
|
||||
|
||||
const { mutate: deleteGitHubConnection } = useGitHubConnectionDeleteMutation({
|
||||
onSuccess: () => {
|
||||
toast.success('Successfully deleted Github connection')
|
||||
toast.success('Successfully deleted GitHub connection')
|
||||
},
|
||||
})
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@ import { RevokeAppModal } from './RevokeAppModal'
|
||||
|
||||
// [Joshen] Note on nav UX
|
||||
// Kang Ming mentioned that it might be better to split Published Apps and Authorized Apps into 2 separate tabs
|
||||
// to prevent any confusion (case study: Github). Authorized apps could be in the "integrations" tab, but let's
|
||||
// to prevent any confusion (case study: GitHub). Authorized apps could be in the "integrations" tab, but let's
|
||||
// check in again after we wrap up Vercel integration
|
||||
|
||||
const OAuthApps = () => {
|
||||
|
||||
@@ -17,7 +17,7 @@ export const LibrarySuggestions = ({ library }: LibrarySuggestionsProps) => {
|
||||
<div className="px-6 flex flex-col gap-y-4">
|
||||
<div className="space-y-2">
|
||||
<p className="text-sm text-foreground-light">
|
||||
Found an issue or a bug? Try searching our Github issues or submit a new one.
|
||||
Found an issue or a bug? Try searching our GitHub issues or submit a new one.
|
||||
</p>
|
||||
</div>
|
||||
<div className="flex items-center space-x-4 overflow-x-auto">
|
||||
@@ -37,7 +37,7 @@ export const LibrarySuggestions = ({ library }: LibrarySuggestionsProps) => {
|
||||
<div>
|
||||
<Button asChild type="default" icon={<ExternalLink size={14} strokeWidth={1.5} />}>
|
||||
<Link href={lib.url} target="_blank" rel="noreferrer">
|
||||
View Github issues
|
||||
View GitHub issues
|
||||
</Link>
|
||||
</Button>
|
||||
</div>
|
||||
@@ -57,7 +57,7 @@ export const LibrarySuggestions = ({ library }: LibrarySuggestionsProps) => {
|
||||
<div>
|
||||
<Button asChild type="default" icon={<ExternalLink size={14} strokeWidth={1.5} />}>
|
||||
<Link href="https://github.com/supabase/supabase" target="_blank" rel="noreferrer">
|
||||
View Github issues
|
||||
View GitHub issues
|
||||
</Link>
|
||||
</Button>
|
||||
</div>
|
||||
|
||||
@@ -79,7 +79,7 @@ const Success = ({
|
||||
target="_blank"
|
||||
rel="noreferrer"
|
||||
>
|
||||
Search on Github discussions
|
||||
Search on GitHub discussions
|
||||
</Link>
|
||||
</Button>,
|
||||
]}
|
||||
|
||||
@@ -584,7 +584,7 @@ export const SupportFormV2 = ({
|
||||
rel="noreferrer"
|
||||
className="flex items-center gap-x-1 underline hover:text-foreground transition"
|
||||
>
|
||||
Github discussions
|
||||
GitHub discussions
|
||||
<ExternalLink size={14} strokeWidth={2} />
|
||||
</Link>
|
||||
<span> for a quick answer</span>
|
||||
|
||||
@@ -230,7 +230,7 @@ export const BranchDropdown = () => {
|
||||
<MessageCircle size={14} strokeWidth={1} className="text-muted mt-0.5" />
|
||||
<div>
|
||||
<p>Branching feedback</p>
|
||||
<p className="text-lighter">Join Github Discussion</p>
|
||||
<p className="text-lighter">Join GitHub Discussion</p>
|
||||
</div>
|
||||
</a>
|
||||
</CommandItem_Shadcn_>
|
||||
|
||||
@@ -48,7 +48,7 @@ export const useCheckGithubBranchValidity = ({
|
||||
},
|
||||
async onError(data, variables, context) {
|
||||
if (onError === undefined) {
|
||||
toast.error(`Failed to check Github branch: ${data.message}`)
|
||||
toast.error(`Failed to check GitHub branch: ${data.message}`)
|
||||
} else {
|
||||
onError(data, variables, context)
|
||||
}
|
||||
|
||||
@@ -44,7 +44,7 @@ export const useGitHubConnectionCreateMutation = ({
|
||||
},
|
||||
async onError(data, variables, context) {
|
||||
if (onError === undefined) {
|
||||
toast.error(`Failed to create Github connection: ${data.message}`)
|
||||
toast.error(`Failed to create GitHub connection: ${data.message}`)
|
||||
} else {
|
||||
onError(data, variables, context)
|
||||
}
|
||||
|
||||
@@ -44,7 +44,7 @@ export const useGitHubConnectionDeleteMutation = ({
|
||||
},
|
||||
async onError(data, variables, context) {
|
||||
if (onError === undefined) {
|
||||
toast.error(`Failed to delete Github connection: ${data.message}`)
|
||||
toast.error(`Failed to delete GitHub connection: ${data.message}`)
|
||||
} else {
|
||||
onError(data, variables, context)
|
||||
}
|
||||
|
||||
@@ -50,7 +50,7 @@ export const useGitHubConnectionUpdateMutation = ({
|
||||
},
|
||||
async onError(data, variables, context) {
|
||||
if (onError === undefined) {
|
||||
toast.error(`Failed to update Github connection: ${data.message}`)
|
||||
toast.error(`Failed to update GitHub connection: ${data.message}`)
|
||||
} else {
|
||||
onError(data, variables, context)
|
||||
}
|
||||
|
||||
@@ -112,7 +112,7 @@ Sentry.init({
|
||||
// [Joshen] Seems to be from hcaptcha
|
||||
"undefined is not an object (evaluating 'n.chat.setReady')",
|
||||
"undefined is not an object (evaluating 'i.chat.setReady')",
|
||||
// [Terry] When users paste in an embedded Github Gist
|
||||
// [Terry] When users paste in an embedded GitHub Gist
|
||||
// Error thrown by `sql-formatter` lexer when given invalid input
|
||||
// Original format: new Error(`Parse error: Unexpected "${text}" at line ${line} column ${col}`)
|
||||
/^Parse error: Unexpected ".+" at line \d+ column \d+$/,
|
||||
|
||||
@@ -24,7 +24,7 @@ export default async function handler(
|
||||
req: NextApiRequest,
|
||||
res: NextApiResponse<{ commitSha: string; commitTime: string }>
|
||||
) {
|
||||
// Set cache control headers for 10 minutes so that we don't get banned by Github API
|
||||
// Set cache control headers for 10 minutes so that we don't get banned by GitHub API
|
||||
res.setHeader('Cache-Control', 's-maxage=600')
|
||||
|
||||
// Get the build commit SHA from Vercel environment variable
|
||||
|
||||
@@ -23,7 +23,7 @@ const SocialAuthDemo = () => {
|
||||
<div className="flex flex-col gap-6">
|
||||
{error && <p className="text-sm text-destructive-500">{error}</p>}
|
||||
<Button type="submit" className="w-full" disabled={isLoading}>
|
||||
{isLoading ? 'Logging in...' : 'Continue with Github'}
|
||||
{isLoading ? 'Logging in...' : 'Continue with GitHub'}
|
||||
</Button>
|
||||
</div>
|
||||
</form>
|
||||
|
||||
@@ -6,7 +6,7 @@ description: Social authentication block for React Router
|
||||
<BlockPreview name="social-auth/auth/login" />
|
||||
|
||||
<Callout className="mt-4">
|
||||
The block is using Github provider by default, but can be easily switched by changing a single
|
||||
The block is using GitHub provider by default, but can be easily switched by changing a single
|
||||
parameter.
|
||||
</Callout>
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ description: Social authentication block for React Single Page Applications
|
||||
<BlockPreview name="social-auth/auth/login" />
|
||||
|
||||
<Callout className="mt-4">
|
||||
The block is using Github provider by default, but can be easily switched by changing a single
|
||||
The block is using GitHub provider by default, but can be easily switched by changing a single
|
||||
parameter.
|
||||
</Callout>
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ description: Social authentication block for Tanstack Start
|
||||
<BlockPreview name="social-auth/auth/login" />
|
||||
|
||||
<Callout className="mt-4">
|
||||
The block is using Github provider by default, but can be easily switched by changing a single
|
||||
The block is using GitHub provider by default, but can be easily switched by changing a single
|
||||
parameter.
|
||||
</Callout>
|
||||
|
||||
|
||||
@@ -49,7 +49,7 @@ export function LoginForm({ className, ...props }: React.ComponentPropsWithoutRe
|
||||
<div className="flex flex-col gap-6">
|
||||
{error && <p className="text-sm text-destructive-500">{error}</p>}
|
||||
<Button type="submit" className="w-full" disabled={isLoading}>
|
||||
{isLoading ? 'Logging in...' : 'Continue with Github'}
|
||||
{isLoading ? 'Logging in...' : 'Continue with GitHub'}
|
||||
</Button>
|
||||
</div>
|
||||
</form>
|
||||
|
||||
@@ -51,7 +51,7 @@ export default function Login() {
|
||||
<div className="flex flex-col gap-6">
|
||||
{error && <p className="text-sm text-destructive-500">{error}</p>}
|
||||
<Button type="submit" className="w-full" disabled={loading}>
|
||||
{loading ? 'Logging in...' : 'Continue with Github'}
|
||||
{loading ? 'Logging in...' : 'Continue with GitHub'}
|
||||
</Button>
|
||||
</div>
|
||||
</fetcher.Form>
|
||||
|
||||
@@ -47,7 +47,7 @@ export function LoginForm({ className, ...props }: React.ComponentPropsWithoutRe
|
||||
<div className="flex flex-col gap-6">
|
||||
{error && <p className="text-sm text-destructive-500">{error}</p>}
|
||||
<Button type="submit" className="w-full" disabled={isLoading}>
|
||||
{isLoading ? 'Logging in...' : 'Continue with Github'}
|
||||
{isLoading ? 'Logging in...' : 'Continue with GitHub'}
|
||||
</Button>
|
||||
</div>
|
||||
</form>
|
||||
|
||||
@@ -47,7 +47,7 @@ export function LoginForm({ className, ...props }: React.ComponentPropsWithoutRe
|
||||
<div className="flex flex-col gap-6">
|
||||
{error && <p className="text-sm text-destructive-500">{error}</p>}
|
||||
<Button type="submit" className="w-full" disabled={isLoading}>
|
||||
{isLoading ? 'Logging in...' : 'Continue with Github'}
|
||||
{isLoading ? 'Logging in...' : 'Continue with GitHub'}
|
||||
</Button>
|
||||
</div>
|
||||
</form>
|
||||
|
||||
@@ -33,7 +33,7 @@ Before we dive in, let's look at some prerequisites you'll need:
|
||||
|
||||
## Loading data into Supabase using Python
|
||||
|
||||
Supabase is built for developers, and you can [get started for free](https://supabase.com/dashboard) using your existing Github account. Once your Supabase account is set up, you will access the Supabase dashboard. From here, go to All Project > New Project.
|
||||
Supabase is built for developers, and you can [get started for free](https://supabase.com/dashboard) using your existing GitHub account. Once your Supabase account is set up, you will access the Supabase dashboard. From here, go to All Project > New Project.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ In order to build this chat app, we will need a database to store all of the cha
|
||||
|
||||
This article also assumes that you have installed Flutter already on your machine. If not, you can go to the [official Flutter page](https://docs.flutter.dev/get-started/install) to start the installation.
|
||||
|
||||
You can find the complete version of this app in [this](https://github.com/supabase-community/flutter-chat) Github repository.
|
||||
You can find the complete version of this app in [this](https://github.com/supabase-community/flutter-chat) GitHub repository.
|
||||
|
||||
## Overview of the final chat app
|
||||
|
||||
@@ -74,7 +74,7 @@ Run `flutter pub get` to install the packages. Note that you will have to termin
|
||||
|
||||
If you do not have a Supabase account yet, do not worry, you can [get started for free](https://supabase.com/dashboard/).
|
||||
|
||||
You will be prompted to sign in using your Github account with a big green button, so let's go ahead and press it. Proceed with the sign up process and once you are done, you will be taken to a list of projects. You can go ahead and create a new project by pressing the “New Project” button at the top.
|
||||
You will be prompted to sign in using your GitHub account with a big green button, so let's go ahead and press it. Proceed with the sign up process and once you are done, you will be taken to a list of projects. You can go ahead and create a new project by pressing the “New Project” button at the top.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -32,7 +32,7 @@ Supabase Flutter SDK is getting a major update, with a big focus on developer ex
|
||||
|
||||
|
||||
|
||||
We've been hard at work making an Auth experience that is as smooth as possible for Supabase developers. The new Auth Helpers have a better experience for server-side rendering (SSR) environments, new Github structure, SvelteKit support, and more. [Read the blog](https://supabase.com/blog/supabase-auth-helpers-with-sveltekit-support).
|
||||
We've been hard at work making an Auth experience that is as smooth as possible for Supabase developers. The new Auth Helpers have a better experience for server-side rendering (SSR) environments, new GitHub structure, SvelteKit support, and more. [Read the blog](https://supabase.com/blog/supabase-auth-helpers-with-sveltekit-support).
|
||||
|
||||
## pg_jsonschema – A Postgres extension for JSON validation
|
||||
|
||||
|
||||
@@ -38,9 +38,9 @@ It is also much easier to become-and remain-SOC2 compliant when you institute th
|
||||
|
||||
## Choosing a compliance monitoring tool
|
||||
|
||||
There are a few tools that plug into your cloud providers, task management system, identity, and HR providers and make it easy to monitor, collect and submit evidence to auditors. We evaluated [Vanta](https://www.vanta.com/), [Drata](https://drata.com/), [Secureframe](https://secureframe.com/), and [Tugboat Logic](https://tugboatlogic.com/). Our stack is pretty standard (AWS, GCP, GSuite, and Github). All the tools we evaluated were integrated with these systems.
|
||||
There are a few tools that plug into your cloud providers, task management system, identity, and HR providers and make it easy to monitor, collect and submit evidence to auditors. We evaluated [Vanta](https://www.vanta.com/), [Drata](https://drata.com/), [Secureframe](https://secureframe.com/), and [Tugboat Logic](https://tugboatlogic.com/). Our stack is pretty standard (AWS, GCP, GSuite, and GitHub). All the tools we evaluated were integrated with these systems.
|
||||
|
||||
Some of them had overly broad permissions when integrating with our vendors (read/write access to Github for example) which made them a no-go. Some came with a lightweight agent that we could use for Mobile Device Management (MDM). Other than that, the products are largely the same.
|
||||
Some of them had overly broad permissions when integrating with our vendors (read/write access to GitHub for example) which made them a no-go. Some came with a lightweight agent that we could use for Mobile Device Management (MDM). Other than that, the products are largely the same.
|
||||
|
||||
We chose Vanta, with Drata coming in a close second. Vanta supported more compliance standards (at that time) and is a fellow YC company (which sealed the deal). The gap between these tools is much closer now since all of them support the compliance standards we have our eyes on.
|
||||
|
||||
|
||||
@@ -40,7 +40,7 @@ Along our jurney we will:
|
||||
</div>
|
||||
Watch the video version of the tutorial.
|
||||
|
||||
Since there are quite some code snippets we need I've put together the [full source code on Github](https://github.com/saimon24/supabase-trello-angular) so you can easily run the project yourself!
|
||||
Since there are quite some code snippets we need I've put together the [full source code on GitHub](https://github.com/saimon24/supabase-trello-angular) so you can easily run the project yourself!
|
||||
|
||||
If you are not familiar with [Trello](https://trello.com/), it's a way to manage projects with different boards, lists and cards!
|
||||
|
||||
@@ -1384,7 +1384,7 @@ With that final piece of code we are completely done with our Supabase Angular T
|
||||
|
||||
Building projects with Supabase is awesome, and hopefully this real world clone example gave you insight into different areas that you need to think about.
|
||||
|
||||
You can [find the full code of this tutorial on Github](https://github.com/saimon24/supabase-trello-angular) where you just need to insert your own Supabase instance and then create the tables with the included SQL file.
|
||||
You can [find the full code of this tutorial on GitHub](https://github.com/saimon24/supabase-trello-angular) where you just need to insert your own Supabase instance and then create the tables with the included SQL file.
|
||||
|
||||
If you enjoyed the tutorial, you can [find many more tutorials on my YouTube channel](https://www.youtube.com/simongrimmdev_) where I help web developers build awesome mobile apps.
|
||||
|
||||
|
||||
@@ -26,7 +26,7 @@ It's pretty rare for a company to stop feature development altogether, but lucki
|
||||
|
||||
We saw a lot of progress across our Open Issues - closing over 250 issues and 50 Pull Requests.
|
||||
|
||||
|
||||
|
||||
|
||||
and we shipped a few things:
|
||||
|
||||
|
||||
@@ -33,7 +33,7 @@ If you are not yet familiar with Ionic you can check out the [Ionic Quickstart g
|
||||
|
||||
However, most of the logic is Angular based and therefore applies to any Angular web project as well.
|
||||
|
||||
You can [find the full code of this tutorial on Github](https://github.com/saimon24/supa-chat) where you just need to insert your own Supabase instance and then create the tables with the included SQL file.
|
||||
You can [find the full code of this tutorial on GitHub](https://github.com/saimon24/supa-chat) where you just need to insert your own Supabase instance and then create the tables with the included SQL file.
|
||||
|
||||
But before we dive into the app, let's set up our Supabase project!
|
||||
|
||||
@@ -1316,7 +1316,7 @@ ion-textarea {
|
||||
}
|
||||
```
|
||||
|
||||
You can [find the full code of this tutorial on Github](https://github.com/saimon24/supa-chat) including the file for that pattern so your page looks almost like WhatsApp!
|
||||
You can [find the full code of this tutorial on GitHub](https://github.com/saimon24/supa-chat) including the file for that pattern so your page looks almost like WhatsApp!
|
||||
|
||||
|
||||
|
||||
@@ -1517,7 +1517,7 @@ This was the last missing piece, and now you even got seamless Supabase authenti
|
||||
|
||||
We've come a long way and covered everything from setting up tables, to defining policies to protect data, and handling authentication in Ionic Angular applications.
|
||||
|
||||
You can [find the full code of this tutorial on Github](https://github.com/saimon24/supa-chat) where you just need to insert your own Supabase instance and then create the tables with the included SQL file, plus updating the authentication settings as we did in the tutorial
|
||||
You can [find the full code of this tutorial on GitHub](https://github.com/saimon24/supa-chat) where you just need to insert your own Supabase instance and then create the tables with the included SQL file, plus updating the authentication settings as we did in the tutorial
|
||||
|
||||
Although we can now use magic link auth, something probably even better fitting for native apps would be [phone auth with Twilio](https://supabase.com/docs/guides/auth/phone-login/twilio) that's also easily possible with Supabase - just like tons of other authentication providers!
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ More than 30 creators participated in creating content in different formats and
|
||||
|
||||
- [A quick look at Supabase](https://twitter.com/Rorstro/status/1600047388852293632) by Ania Kubów.
|
||||
- [Live streaming: Supabase and Sveltekit](https://www.youtube.com/@JamesQQuick/streams) by James Q Quick.
|
||||
- [Perform Database Migration Using Github Actions & Supabase CLI](https://www.youtube.com/watch?v=iCkdtXSeq7A) by Kunal Kushwaha.
|
||||
- [Perform Database Migration Using GitHub Actions & Supabase CLI](https://www.youtube.com/watch?v=iCkdtXSeq7A) by Kunal Kushwaha.
|
||||
- [Supabase Authentication & Realtime Database with Flutter](https://www.youtube.com/watch?v=UTSSYPOd5A0) by Pooja Bhaumik.
|
||||
- [Why I Switched From AWS Cognito To Supabase The Week Before My Startup Launched](https://medium.com/@sleeplessfox/why-i-switched-from-aws-cognito-to-supabase-the-week-before-my-startup-launched-67fdc1eccb8c) by Danilo à Tellinghusen.
|
||||
- [Supabase Crash Course For Python Developers](https://www.youtube.com/watch?v=M6cfT2pqpSc) by Patrick Loeber.
|
||||
|
||||
@@ -93,7 +93,7 @@ Two key features to level up your projects are now available: Custom domains all
|
||||
|
||||
It was great to see so many high-quality projects. The decision wasn't easy, but in the end, the panel of judges chose Depulso as the winner of the Best Overall Project.
|
||||
|
||||
Congratulations 👏 to [@\_iamkarthikeyan](https://twitter.com/_iamkarthikeyan) and [@SindhuMansi](https://twitter.com/SindhuMansi) who get each a Supabase Darkmode Keyboard and the $1500 Github sponsorship!
|
||||
Congratulations 👏 to [@\_iamkarthikeyan](https://twitter.com/_iamkarthikeyan) and [@SindhuMansi](https://twitter.com/SindhuMansi) who get each a Supabase Darkmode Keyboard and the $1500 GitHub sponsorship!
|
||||
|
||||
- [Full list of Winners](https://supabase.com/blog/launch-week-6-hackathon-winners)
|
||||
- [See all the submissions](https://www.madewithsupabase.com/launch-week-6)
|
||||
@@ -107,7 +107,7 @@ Congratulations 👏 to [@\_iamkarthikeyan](https://twitter.com/_iamkarthikeyan)
|
||||
- Build any Front-end like Admin Panel or CRM for your Supabase. [Article](https://blog.jetadmin.io/how-to-build-any-front-end-such-as-admin-panel-or-crm-for-your-supabase-in-minutes/)
|
||||
- Everything Svelte: a course with all you need to know to build a modern web application. [Course](https://www.everythingsvelte.com/)
|
||||
- Edgy Edge Functions: a look at a new Edge Function per week. [Youtube Playlist](https://www.youtube.com/playlist?list=PL5S4mPUpp4OulD3olUW8Eq1IYKpUbk5Ob)
|
||||
- Pixels, an app that provides canvas to create pixel art. [App](https://pixels.refine.dev/) | [Github Repo](https://github.com/refinedev/refine/tree/next/examples/pixels)
|
||||
- Pixels, an app that provides canvas to create pixel art. [App](https://pixels.refine.dev/) | [GitHub Repo](https://github.com/refinedev/refine/tree/next/examples/pixels)
|
||||
- Supabase Angular authentication with RxJS Observables. [Tutorial](https://dev.to/kylerummens/supabase-angular-authentication-with-rxjs-observables-3d0f)
|
||||
- Create Calendar Events in React With Google Calendar API and Supabase. [Video Tutorial](https://www.youtube.com/watch?v=tgcCl52EN84)
|
||||
- Going Serverless with Supabase. [Part 1](https://dev.to/davepar/going-serverless-with-supabase-103h)
|
||||
|
||||
@@ -82,11 +82,11 @@ We teamed up with DigitalOcean to level up self-hosted Supabase. This guide show
|
||||
|
||||
[Get started](https://docs.digitalocean.com/developer-center/hosting-supabase-on-digitalocean/).
|
||||
|
||||
## 45k Github stars (and counting!)
|
||||
## 45k GitHub stars (and counting!)
|
||||
|
||||
|
||||
|
||||
|
||||
We hit two big milestones: 45k stars and Supabase is one the top 200 most-popular repos on Github 💥
|
||||
We hit two big milestones: 45k stars and Supabase is one the top 200 most-popular repos on GitHub 💥
|
||||
|
||||
Massive thanks to the community for all the support 👁️⚡️👁️
|
||||
|
||||
|
||||
@@ -29,7 +29,7 @@ In this tutorial you will learn to:
|
||||
- Display a [Capacitor Google Map](https://capacitorjs.com/docs/apis/google-maps) with a marker
|
||||
- Upload files to Supabase Storage and use [image transformations](https://supabase.com/docs/guides/storage/serving/image-transformations)
|
||||
|
||||
Since there are quite some code snippets we need I've put together the [full source code on Github](https://github.com/saimon24/supabase-postgis-ionic-angular) so you can easily run the project yourself!
|
||||
Since there are quite some code snippets we need I've put together the [full source code on GitHub](https://github.com/saimon24/supabase-postgis-ionic-angular) so you can easily run the project yourself!
|
||||
|
||||
Ready for some action?
|
||||
|
||||
@@ -1030,7 +1030,7 @@ I was fascinated by the power of this simple PostGIS extension that we enabled w
|
||||
Building apps based on geolocation data is a very common scenario, and with PostGIS we can build these applications easily on the back of a [Supabase](https://supabase.com/) database (and [auth](https://supabase.com/blog/authentication-in-ionic-angular)
|
||||
), and storage, and so much more..)
|
||||
|
||||
You can [find the full code of this tutorial on Github](https://github.com/saimon24/supabase-postgis-ionic-angular) where you just need to insert your own Supabase instance. your Google Maps key and then create the tables with the included SQL file.
|
||||
You can [find the full code of this tutorial on GitHub](https://github.com/saimon24/supabase-postgis-ionic-angular) where you just need to insert your own Supabase instance. your Google Maps key and then create the tables with the included SQL file.
|
||||
|
||||
If you enjoyed the tutorial, you can [find many more tutorials and courses on Galaxies.dev](https://galaxies.dev) where I help modern web and mobile developers build epic apps 🚀
|
||||
|
||||
|
||||
@@ -26,7 +26,7 @@ In this tutorial, you will learn to:
|
||||
- Work with Expo Router v2 and protected routes
|
||||
- Upload files to [Supabase Storage](https://supabase.com/docs/guides/storage)
|
||||
|
||||
You can also directly check out the [full source code on Github](https://github.com/saimon24/react-native-resumable-upload-supabase) so you can get started with Supabase fast!
|
||||
You can also directly check out the [full source code on GitHub](https://github.com/saimon24/react-native-resumable-upload-supabase) so you can get started with Supabase fast!
|
||||
|
||||
Before we get into the app, let's quickly [start a new Supabase project](https://supabase.com/dashboard).
|
||||
|
||||
@@ -606,7 +606,7 @@ It's almost too easy to use Supabase Storage, and it's a great way to store file
|
||||
|
||||
You now have a fully functional image gallery app with React Native and Supabase Storage including user authentication without writing a line of backend code!
|
||||
|
||||
You can [find the full code of this tutorial on Github](https://github.com/saimon24/react-native-resumable-upload-supabase) where you just need to insert your own Supabase URL and API key.
|
||||
You can [find the full code of this tutorial on GitHub](https://github.com/saimon24/react-native-resumable-upload-supabase) where you just need to insert your own Supabase URL and API key.
|
||||
|
||||
If you enjoyed the tutorial, you can [learn React Native on Galaxies.dev](https://galaxies.dev) where I help developers build awesome React Native apps.
|
||||
|
||||
|
||||
@@ -99,7 +99,7 @@ Along with these huge AI features, we also added a bunch of new improvements els
|
||||
|
||||
For a while now, many Supabase users have been using [Zernonia's](https://github.com/zernonia) [Supabase Schema visualization tool](https://supabase-schema.vercel.app/). While this was an amazing tool, many users wanted to see something like this directly integrated into the Studio.
|
||||
|
||||
We opened an [Issue for it on Github](https://github.com/supabase/supabase/issues/15585) and within a day or two the wheels were in motion. After a couple of weeks, the feature was polished up and merged. It's inspiring to see the power of open source at work. This feature wasn't trivial, and to see community members take it from feature request to production in just a couple of weeks is mind-blowing. Unquestionably, we have one of the best open source communities out there. Huge thanks to [kamilogorek](https://github.com/kamilogorek) and [adiologydev](https://github.com/adiologydev) for their work on this!
|
||||
We opened an [Issue for it on GitHub](https://github.com/supabase/supabase/issues/15585) and within a day or two the wheels were in motion. After a couple of weeks, the feature was polished up and merged. It's inspiring to see the power of open source at work. This feature wasn't trivial, and to see community members take it from feature request to production in just a couple of weeks is mind-blowing. Unquestionably, we have one of the best open source communities out there. Huge thanks to [kamilogorek](https://github.com/kamilogorek) and [adiologydev](https://github.com/adiologydev) for their work on this!
|
||||
|
||||
Special thanks as well to [Zernonia](https://twitter.com/zernonia) for providing the inspiration for this great new feature! OSS FTW.
|
||||
|
||||
|
||||
@@ -344,7 +344,7 @@ export default function Auth() {
|
||||
|
||||
return (
|
||||
<>
|
||||
<Button onPress={performOAuth} title="Sign in with Github" />
|
||||
<Button onPress={performOAuth} title="Sign in with GitHub" />
|
||||
<Button onPress={sendMagicLink} title="Send Magic Link" />
|
||||
</>
|
||||
)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 'GitHub OAuth in your Python Flask app'
|
||||
description: A step-by-step guide on building Login with Github into your Python apps.
|
||||
description: A step-by-step guide on building Login with GitHub into your Python apps.
|
||||
categories:
|
||||
- developers
|
||||
tags:
|
||||
|
||||
@@ -168,7 +168,7 @@ If you use Realtime, you'll find the new inspector very handy. Please send along
|
||||
|
||||
## Feature Previews
|
||||
|
||||
Today we're releasing **Feature Previews**, our tool for unveiling new features. We release beta features as Previews before making them generally available. You can see a list of features that are available for preview along with a screenshot and a brief description. Each feature includes a link to a Github Discussion for feedback.
|
||||
Today we're releasing **Feature Previews**, our tool for unveiling new features. We release beta features as Previews before making them generally available. You can see a list of features that are available for preview along with a screenshot and a brief description. Each feature includes a link to a GitHub Discussion for feedback.
|
||||
|
||||
We have a couple of goals with Feature Previews. We want to:
|
||||
|
||||
@@ -194,7 +194,7 @@ We currently have two features in preview:
|
||||
|
||||
<Img src="/images/blog/launch-week-x/day-1/10.png" alt="Supabase AI revised API side panel" />
|
||||
|
||||
We'll be actively keeping an eye on the Github Discussions and will be responding to your feedback.
|
||||
We'll be actively keeping an eye on the GitHub Discussions and will be responding to your feedback.
|
||||
|
||||
## Wrapping up
|
||||
|
||||
|
||||
@@ -110,7 +110,7 @@ These features were essential for Supabase, and since the [TUS node server](http
|
||||
# Getting started
|
||||
|
||||
- Check out the S3 API compatibility [in our docs](/docs/guides/storage/s3/compatibility)
|
||||
- Request a feature on the [Storage Github repo](https://github.com/supabase/storage)
|
||||
- Request a feature on the [Storage GitHub repo](https://github.com/supabase/storage)
|
||||
- Learn about [S3 Authentication](/docs/guides/storage/s3/authentication)
|
||||
- Try S3 with Cyberduck: follow our [integration guide](/partners/integrations/cyberduck)
|
||||
- Try S3 with DuckDB: follow the guide [on YouTube](https://www.youtube.com/watch?v=diL00ZZ-q50)
|
||||
|
||||
@@ -131,7 +131,7 @@ using (
|
||||
);
|
||||
```
|
||||
|
||||
Reference our [Github Discussion](https://github.com/orgs/supabase/discussions/22484) for more complex use cases.
|
||||
Reference our [GitHub Discussion](https://github.com/orgs/supabase/discussions/22484) for more complex use cases.
|
||||
|
||||
### 2. Enabling Authorization on Channels
|
||||
|
||||
|
||||
@@ -83,7 +83,7 @@ Log Drains are available as an project Add-On for all Team and Enterprise users.
|
||||
|
||||
## Roadmap
|
||||
|
||||
- We intend to support a wide variety of destinations. Syslog and [Loki](https://github.com/grafana/loki) are currently under development and are expected to be released in the coming weeks. If you would like your favorite tools to be supported as a destination, vote on [this Github discussion](https://github.com/orgs/supabase/discussions/28324)!
|
||||
- We intend to support a wide variety of destinations. Syslog and [Loki](https://github.com/grafana/loki) are currently under development and are expected to be released in the coming weeks. If you would like your favorite tools to be supported as a destination, vote on [this GitHub discussion](https://github.com/orgs/supabase/discussions/28324)!
|
||||
- Log sampling to control the volume of logs sent to the drain
|
||||
- Draining specific product logs
|
||||
- Sharing Log Drains between multiple projects
|
||||
|
||||
@@ -84,7 +84,7 @@ A CLI tool to automate manual effort/repetitive things when using Supabase.
|
||||
|
||||
### Runner Up
|
||||
|
||||
[Github RAG](https://github.com/XamHans/github-rag) by [Johannes Hayer](https://twitter.com/Hayer_Hans)
|
||||
[GitHub RAG](https://github.com/XamHans/github-rag) by [Johannes Hayer](https://twitter.com/Hayer_Hans)
|
||||
|
||||
This project allows you to chat with your starred GitHub repositories to easily find the repos you need. It utilizes RAG
|
||||
|
||||
|
||||
@@ -73,7 +73,7 @@ The Supabase website uses several [Edge Functions](https://github.com/supabase/s
|
||||
verify_jwt = false
|
||||
```
|
||||
|
||||
If you are using a monorepo (like the [@supabase/supabase](https://github.com/supabase/supabase) Github repository), you may also want to customize the paths to your function’s entrypoint and import map files. This is especially useful for code sharing between your frontend application and Edge Functions.
|
||||
If you are using a monorepo (like the [@supabase/supabase](https://github.com/supabase/supabase) GitHub repository), you may also want to customize the paths to your function’s entrypoint and import map files. This is especially useful for code sharing between your frontend application and Edge Functions.
|
||||
|
||||
<Admonition type="tip" title="Setting Edge Function secrets">
|
||||
|
||||
|
||||
@@ -240,7 +240,7 @@ export default (isMobile?: boolean) => ({
|
||||
href="https://supabase.com/docs/guides/functions/cicd-workflow"
|
||||
className="underline hover:text-foreground-light transition-colors"
|
||||
>
|
||||
Supabase CLI with Github actions
|
||||
Supabase CLI with GitHub actions
|
||||
</Link>{' '}
|
||||
to preview and deploy your functions along with the rest of your application
|
||||
</>
|
||||
|
||||
@@ -6,7 +6,7 @@ import { CodeHikeConfig, remarkCodeHike } from '@code-hike/mdx'
|
||||
import codeHikeTheme from 'config/code-hike.theme.json' with { type: 'json' }
|
||||
|
||||
// mdx2 needs self-closing tags.
|
||||
// dragging an image onto a Github discussion creates an <img>
|
||||
// dragging an image onto a GitHub discussion creates an <img>
|
||||
// we need to fix this before running them through mdx
|
||||
// also checks for <br> and <hr>
|
||||
function addSelfClosingTags(htmlString: string): string {
|
||||
|
||||
@@ -70,7 +70,7 @@ After registration, you may create, upload or transmit files, documents, videos,
|
||||
|
||||
We may receive personal information about you from our business partners and service providers and combine this information with other data we collect from you. The third-parties may include website and service operators and payment processors and marketing partners. The information may include contact information, demographic information, information about your communications and related activities, and information about your orders. We may use this information to administer and facilitate our services, your orders and our marketing activities.
|
||||
|
||||
- **_Single Sign-On._** We use single sign-on ("**SSO**") such as Github to allow a user to authenticate their account using one set of login information. We will have access to certain information from those third parties in accordance with the authorization procedures determined by those third parties, including, for example, your name, username, email address, language preference, and profile picture. We use this information to operate, maintain, and provide to you the features and functionality of the Service. We may also send you service-related emails or messages (e.g., account verification, purchase confirmation, customer support, changes or updates to features of the Site, technical and security notices).
|
||||
- **_Single Sign-On._** We use single sign-on ("**SSO**") such as GitHub to allow a user to authenticate their account using one set of login information. We will have access to certain information from those third parties in accordance with the authorization procedures determined by those third parties, including, for example, your name, username, email address, language preference, and profile picture. We use this information to operate, maintain, and provide to you the features and functionality of the Service. We may also send you service-related emails or messages (e.g., account verification, purchase confirmation, customer support, changes or updates to features of the Site, technical and security notices).
|
||||
- **_Social Media._** When you interact with our Site through various social media, such as when you click on the social media icon on the Site, follow us on a social media site, or post a comment to one of our pages, we may receive information from the social network such as your profile information, profile picture, user name, user ID associated with your social media account, and any other information you permit the social network to share with third parties. The data we receive is dependent upon your privacy settings with the social network. We use this information to operate, maintain, and provide to you the features and functionality of the Service, as well as to communicate directly with you, such as to send you email messages about products and services that may be of interest to you.
|
||||
- **_Information from Other Sources._** We may obtain information from other sources, including through third-party information providers, our shareholders, customers, or through transactions such as mergers and acquisitions. We may combine this information with other information we collect from or about you. In these cases, our Privacy Notice governs the handling of the combined personal information. We use this information to operate, maintain, and provide to you the features and functionality of the Service, as well as to communicate directly with you, such as to send you email messages about products and services that may be of interest to you.
|
||||
|
||||
@@ -166,11 +166,11 @@ We collect the following categories of personal information that you submit dire
|
||||
| We use this information to deal with enquiries and complaints made by or about you relating to the Service. | The processing is necessary for our legitimate interests, namely administering the Service, and for communicating with you effectively to respond to your queries or complaints. | |
|
||||
| We use this information to send you marketing communications in accordance with your preferences. | We will only use your personal information in this way to the extent you have given us consent to do so. | |
|
||||
|
||||
(b) **Your registration / account information**. When you create an account and access the Service as an individual, If you use an email and password to sign up to the service we will collect your email address, and password. If you use Github we use single sign-on ("**_SSO_**") such as Github to allow a user to authenticate their account using one set of login information. The data we receive is dependent on your privacy settings with the social network.
|
||||
(b) **Your registration / account information**. When you create an account and access the Service as an individual, If you use an email and password to sign up to the service we will collect your email address, and password. If you use GitHub we use single sign-on ("**_SSO_**") such as GitHub to allow a user to authenticate their account using one set of login information. The data we receive is dependent on your privacy settings with the social network.
|
||||
|
||||
| **How we may use the Personal Information** | **Legal Bases for Processing** | **Recipients of Personal Information** |
|
||||
| -------------------------------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| We use this information to create your account on the Service. | The processing is necessary for the performance of a contract with you. | We may share this information with the following service providers through the provision of the Service: Github, Amazon Web Services. |
|
||||
| We use this information to create your account on the Service. | The processing is necessary for the performance of a contract with you. | We may share this information with the following service providers through the provision of the Service: GitHub, Amazon Web Services. |
|
||||
|
||||
(c) **Payment transaction and billing information**. When you make a purchase through your own individual account on the Service, we collect information such as your billing address and Tax ID and other information such as date and time of your transaction and products / services purchased.
|
||||
|
||||
@@ -193,11 +193,11 @@ We collect the following categories of personal information that you submit dire
|
||||
| When you use the Supabase AI to submit queries through your own individual account, we will use this information to generate automated responses to your query. | The processing is necessary for the performance of a contract with you, namely our Terms of Service. | We may share this information with the following service providers through the provision of the Service: OpenAI, LLC and its affiliates, Fly.io, and AWS. |
|
||||
| We this information to assess the performance of the chatbot tool and improve the Service. | The processing is necessary for our legitimate interests (to develop and improve our service). | |
|
||||
|
||||
(f) **Information received from third parties, such as social networks**. If you interact with us through a social network, we may receive information from the social network such as your name, profile information, and any other information you permit the social network to share with third parties. We use single sign-on ("**_SSO_**") such as Github to allow a user to authenticate their account using one set of login information. The data we receive is dependent on your privacy settings with the social network.
|
||||
(f) **Information received from third parties, such as social networks**. If you interact with us through a social network, we may receive information from the social network such as your name, profile information, and any other information you permit the social network to share with third parties. We use single sign-on ("**_SSO_**") such as GitHub to allow a user to authenticate their account using one set of login information. The data we receive is dependent on your privacy settings with the social network.
|
||||
|
||||
| **How we may use the Personal Information** | **Legal Bases for Processing** | **Recipients of Personal Information** |
|
||||
| ---------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| We use this information to reshare content created through the use of the Service. | The processing is necessary for our legitimate interests (to develop our service and inform our marketing strategy). | We may share this information with the following service providers through the provision of the Service: Commonroom, Github, and Slack. |
|
||||
| We use this information to reshare content created through the use of the Service. | The processing is necessary for our legitimate interests (to develop our service and inform our marketing strategy). | We may share this information with the following service providers through the provision of the Service: Commonroom, GitHub, and Slack. |
|
||||
| We use this information to authenticate you and allow you to access the Service. | The processing is necessary for the performance of a contract with you. | |
|
||||
|
||||
### 2. Information we collect about your Use of the Site and Service.
|
||||
|
||||
@@ -70,7 +70,7 @@ After registration, you may create, upload or transmit files, documents, videos,
|
||||
|
||||
We may receive personal information about you from our business partners and service providers and combine this information with other data we collect from you. The third-parties may include website and service operators and payment processors and marketing partners. The information may include contact information, demographic information, information about your communications and related activities, and information about your orders. We may use this information to administer and facilitate our services, your orders and our marketing activities.
|
||||
|
||||
- **_Single Sign-On._** We use single sign-on ("**SSO**") such as Github to allow a user to authenticate their account using one set of login information. We will have access to certain information from those third parties in accordance with the authorization procedures determined by those third parties, including, for example, your name, username, email address, language preference, and profile picture. We use this information to operate, maintain, and provide to you the features and functionality of the Service. We may also send you service-related emails or messages (e.g., account verification, purchase confirmation, customer support, changes or updates to features of the Site, technical and security notices).
|
||||
- **_Single Sign-On._** We use single sign-on ("**SSO**") such as GitHub to allow a user to authenticate their account using one set of login information. We will have access to certain information from those third parties in accordance with the authorization procedures determined by those third parties, including, for example, your name, username, email address, language preference, and profile picture. We use this information to operate, maintain, and provide to you the features and functionality of the Service. We may also send you service-related emails or messages (e.g., account verification, purchase confirmation, customer support, changes or updates to features of the Site, technical and security notices).
|
||||
- **_Social Media._** When you interact with our Site through various social media, such as when you click on the social media icon on the Site, follow us on a social media site, or post a comment to one of our pages, we may receive information from the social network such as your profile information, profile picture, user name, user ID associated with your social media account, and any other information you permit the social network to share with third parties. The data we receive is dependent upon your privacy settings with the social network. We use this information to operate, maintain, and provide to you the features and functionality of the Service, as well as to communicate directly with you, such as to send you email messages about products and services that may be of interest to you.
|
||||
- **_Information from Other Sources._** We may obtain information from other sources, including through third-party information providers, our shareholders, customers, or through transactions such as mergers and acquisitions. We may combine this information with other information we collect from or about you. In these cases, our Privacy Notice governs the handling of the combined personal information. We use this information to operate, maintain, and provide to you the features and functionality of the Service, as well as to communicate directly with you, such as to send you email messages about products and services that may be of interest to you.
|
||||
|
||||
@@ -166,11 +166,11 @@ We collect the following categories of personal information that you submit dire
|
||||
| We use this information to deal with enquiries and complaints made by or about you relating to the Service. | The processing is necessary for our legitimate interests, namely administering the Service, and for communicating with you effectively to respond to your queries or complaints. | |
|
||||
| We use this information to send you marketing communications in accordance with your preferences. | We will only use your personal information in this way to the extent you have given us consent to do so. | |
|
||||
|
||||
(b) **Your registration / account information**. When you create an account and access the Service as an individual, If you use an email and password to sign up to the service we will collect your email address, and password. If you use Github we use single sign-on ("**_SSO_**") such as Github to allow a user to authenticate their account using one set of login information. The data we receive is dependent on your privacy settings with the social network.
|
||||
(b) **Your registration / account information**. When you create an account and access the Service as an individual, If you use an email and password to sign up to the service we will collect your email address, and password. If you use GitHub we use single sign-on ("**_SSO_**") such as GitHub to allow a user to authenticate their account using one set of login information. The data we receive is dependent on your privacy settings with the social network.
|
||||
|
||||
| **How we may use the Personal Information** | **Legal Bases for Processing** | **Recipients of Personal Information** |
|
||||
| -------------------------------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| We use this information to create your account on the Service. | The processing is necessary for the performance of a contract with you. | We may share this information with the following service providers through the provision of the Service: Github, Amazon Web Services. |
|
||||
| We use this information to create your account on the Service. | The processing is necessary for the performance of a contract with you. | We may share this information with the following service providers through the provision of the Service: GitHub, Amazon Web Services. |
|
||||
|
||||
(c) **Payment transaction and billing information**. When you make a purchase through your own individual account on the Service, we collect information such as your billing address and Tax ID and other information such as date and time of your transaction and products / services purchased.
|
||||
|
||||
@@ -193,11 +193,11 @@ We collect the following categories of personal information that you submit dire
|
||||
| When you use the Supabase AI to submit queries through your own individual account, we will use this information to generate automated responses to your query. | The processing is necessary for the performance of a contract with you, namely our Terms of Service. | We may share this information with the following service providers through the provision of the Service: OpenAI, LLC and its affiliates, Fly.io, and AWS. |
|
||||
| We this information to assess the performance of the chatbot tool and improve the Service. | The processing is necessary for our legitimate interests (to develop and improve our service). | |
|
||||
|
||||
(f) **Information received from third parties, such as social networks**. If you interact with us through a social network, we may receive information from the social network such as your name, profile information, and any other information you permit the social network to share with third parties. We use single sign-on ("**_SSO_**") such as Github to allow a user to authenticate their account using one set of login information. The data we receive is dependent on your privacy settings with the social network.
|
||||
(f) **Information received from third parties, such as social networks**. If you interact with us through a social network, we may receive information from the social network such as your name, profile information, and any other information you permit the social network to share with third parties. We use single sign-on ("**_SSO_**") such as GitHub to allow a user to authenticate their account using one set of login information. The data we receive is dependent on your privacy settings with the social network.
|
||||
|
||||
| **How we may use the Personal Information** | **Legal Bases for Processing** | **Recipients of Personal Information** |
|
||||
| ---------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| We use this information to reshare content created through the use of the Service. | The processing is necessary for our legitimate interests (to develop our service and inform our marketing strategy). | We may share this information with the following service providers through the provision of the Service: Commonroom, Github, and Slack. |
|
||||
| We use this information to reshare content created through the use of the Service. | The processing is necessary for our legitimate interests (to develop our service and inform our marketing strategy). | We may share this information with the following service providers through the provision of the Service: Commonroom, GitHub, and Slack. |
|
||||
| We use this information to authenticate you and allow you to access the Service. | The processing is necessary for the performance of a contract with you. | |
|
||||
|
||||
### 2. Information we collect about your Use of the Site and Service.
|
||||
|
||||
@@ -72,7 +72,7 @@ After registration, you may create, upload or transmit files, documents, videos,
|
||||
|
||||
We may receive personal information about you from our business partners and service providers and combine this information with other data we collect from you. The third-parties may include website and service operators, payment processors, and marketing partners. The information may include contact information, demographic information, information about your communications and related activities, and information about your orders. We may use this information to administer and facilitate our services, your orders and our marketing activities.
|
||||
|
||||
- **_Single Sign-On._** We use single sign-on ("**SSO**") such as Github to allow a user to authenticate their account using one set of login information. We will have access to certain information from those third parties in accordance with the authorization procedures determined by those third parties, including, for example, your name, username, email address, language preference, and profile picture. We use this information to operate, maintain, and provide to you the features and functionality of the Service. We may also send you service-related emails or messages (e.g., account verification, purchase confirmation, customer support, changes or updates to features of the Site, technical and security notices).
|
||||
- **_Single Sign-On._** We use single sign-on ("**SSO**") such as GitHub to allow a user to authenticate their account using one set of login information. We will have access to certain information from those third parties in accordance with the authorization procedures determined by those third parties, including, for example, your name, username, email address, language preference, and profile picture. We use this information to operate, maintain, and provide to you the features and functionality of the Service. We may also send you service-related emails or messages (e.g., account verification, purchase confirmation, customer support, changes or updates to features of the Site, technical and security notices).
|
||||
- **_Social Media._** When you interact with our Site through various social media, such as when you click on the social media icon on the Site, follow us on a social media site, or post a comment to one of our pages, we may receive information from the social network such as your profile information, profile picture, user name, user ID associated with your social media account, and any other information you permit the social network to share with third parties. The data we receive is dependent upon your privacy settings with the social network. We use this information to operate, maintain, and provide to you the features and functionality of the Service, as well as to communicate directly with you, such as to send you email messages about products and services that may be of interest to you.
|
||||
- **_Information from Other Sources._** We may obtain information from other sources, including through third-party information providers, our shareholders, customers, or through transactions such as mergers and acquisitions. We may combine this information with other information we collect from or about you. In these cases, our Privacy Notice governs the handling of the combined personal information. We use this information to operate, maintain, and provide to you the features and functionality of the Service, as well as to communicate directly with you, such as to send you email messages about products and services that may be of interest to you.
|
||||
|
||||
@@ -168,11 +168,11 @@ We collect the following categories of personal information that you submit dire
|
||||
| We use this information to deal with enquiries and complaints made by or about you relating to the Service. | The processing is necessary for our legitimate interests, namely administering the Service, and for communicating with you effectively to respond to your queries or complaints. | |
|
||||
| We use this information to send you marketing communications in accordance with your preferences. | We will only use your personal information in this way to the extent you have given us consent to do so. | |
|
||||
|
||||
(b) **Your registration / account information**. When you create an account and access the Service as an individual, or if you use an email and password to sign up to the service, we will collect your email address, and password. If you use Github we offer a single sign-on ("**_SSO_**") to allow a user to authenticate their account using one set of login information. The data we receive is dependent on your privacy settings with the social network.
|
||||
(b) **Your registration / account information**. When you create an account and access the Service as an individual, or if you use an email and password to sign up to the service, we will collect your email address, and password. If you use GitHub we offer a single sign-on ("**_SSO_**") to allow a user to authenticate their account using one set of login information. The data we receive is dependent on your privacy settings with the social network.
|
||||
|
||||
| **How we may use the Personal Information** | **Legal Bases for Processing** | **Recipients of Personal Information** |
|
||||
| -------------------------------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| We use this information to create your account on the Service. | The processing is necessary for the performance of a contract with you. | We may share this information with the following service providers through the provision of the Service: Github, Amazon Web Services. |
|
||||
| We use this information to create your account on the Service. | The processing is necessary for the performance of a contract with you. | We may share this information with the following service providers through the provision of the Service: GitHub, Amazon Web Services. |
|
||||
|
||||
(c) **Payment transaction and billing information**. When you make a purchase through your own individual account on the Service, we collect information such as your billing address and Tax ID and other information such as date and time of your transaction and products / services purchased.
|
||||
|
||||
@@ -195,11 +195,11 @@ We collect the following categories of personal information that you submit dire
|
||||
| When you use the Supabase AI to submit queries through your own individual account, we will use this information to generate automated responses to your query. | The processing is necessary for the performance of a contract with you, namely our Terms of Service. | We may share this information with the following service providers through the provision of the Service: OpenAI, LLC and its affiliates, Amazon Bedrock, Fly.io, and AWS. |
|
||||
| We use this information to assess the performance of the chatbot tool and improve the Service. | The processing is necessary for our legitimate interests (to develop and improve our service). | |
|
||||
|
||||
(f) **Information received from third parties, such as social networks**. If you interact with us through a social network, we may receive information from the social network such as your name, profile information, and any other information you permit the social network to share with third parties. We use single sign-on ("**_SSO_**") such as Github to allow a user to authenticate their account using one set of login information. The data we receive is dependent on your privacy settings with the social network.
|
||||
(f) **Information received from third parties, such as social networks**. If you interact with us through a social network, we may receive information from the social network such as your name, profile information, and any other information you permit the social network to share with third parties. We use single sign-on ("**_SSO_**") such as GitHub to allow a user to authenticate their account using one set of login information. The data we receive is dependent on your privacy settings with the social network.
|
||||
|
||||
| **How we may use the Personal Information** | **Legal Bases for Processing** | **Recipients of Personal Information** |
|
||||
| ---------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| We use this information to reshare content created through the use of the Service. | The processing is necessary for our legitimate interests (to develop our service and inform our marketing strategy). | We may share this information with the following service providers through the provision of the Service: Commonroom, Github, and Slack. |
|
||||
| We use this information to reshare content created through the use of the Service. | The processing is necessary for our legitimate interests (to develop our service and inform our marketing strategy). | We may share this information with the following service providers through the provision of the Service: Commonroom, GitHub, and Slack. |
|
||||
| We use this information to authenticate you and allow you to access the Service. | The processing is necessary for the performance of a contract with you. | |
|
||||
|
||||
### 2. Information we collect about your Use of the Site and Service.
|
||||
|
||||
@@ -984,7 +984,7 @@
|
||||
<guid>https://supabase.com/blog/oauth2-login-python-flask-apps</guid>
|
||||
<title>GitHub OAuth in your Python Flask app</title>
|
||||
<link>https://supabase.com/blog/oauth2-login-python-flask-apps</link>
|
||||
<description>A step-by-step guide on building Login with Github into your Python apps.</description>
|
||||
<description>A step-by-step guide on building Login with GitHub into your Python apps.</description>
|
||||
<pubDate>Tue, 21 Nov 2023 00:00:00 -0700</pubDate>
|
||||
</item>
|
||||
<item>
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
Example application on how you can use Realtime Authorization to limit access to Realtime [Channels](https://supabase.com/docs/guides/realtime/concepts#channels) and [Broadcast](https://supabase.com/docs/guides/realtime/broadcast) and [Presence](https://supabase.com/docs/guides/realtime/presence) extensions.
|
||||
|
||||
You can provide feedback on our [Github Discussion](https://github.com/orgs/supabase/discussions/22484).
|
||||
You can provide feedback on our [GitHub Discussion](https://github.com/orgs/supabase/discussions/22484).
|
||||
|
||||
## Objective
|
||||
|
||||
|
||||
@@ -29,7 +29,7 @@ export interface SignUpEvent {
|
||||
}
|
||||
|
||||
/**
|
||||
* Triggered when a user signs in with Github, Email and Password or SSO.
|
||||
* Triggered when a user signs in with GitHub, Email and Password or SSO.
|
||||
*
|
||||
* Some unintuitive behavior:
|
||||
* - If signing up with GitHub the SignInEvent gets triggered first before the SignUpEvent.
|
||||
|
||||
Reference in New Issue
Block a user