From 5b9b22575014e806b0e8b0999d458e84813f2fdb Mon Sep 17 00:00:00 2001 From: benitav Date: Thu, 5 Dec 2024 09:12:46 +0200 Subject: [PATCH 1/3] update iframe --- self-hosting/getting-started.mdx | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/self-hosting/getting-started.mdx b/self-hosting/getting-started.mdx index 79a25ec6..429c5234 100644 --- a/self-hosting/getting-started.mdx +++ b/self-hosting/getting-started.mdx @@ -21,7 +21,17 @@ We have five starting points, detailed below: This video provides a quick introduction to the [PowerSync Open Edition](https://www.powersync.com/blog/powersync-open-edition-release): - + + ## Demo Project (5 minutes) The quickest way to get a feel for the system is to run our example project on your development machine using Docker Compose. You can find it [here](https://github.com/powersync-ja/self-host-demo): From 3ed9c607a80e85d77c276b034748879708bc1a96 Mon Sep 17 00:00:00 2001 From: benitav Date: Thu, 5 Dec 2024 09:15:24 +0200 Subject: [PATCH 2/3] Fix frame error --- snippets/supabase-database-connection.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/snippets/supabase-database-connection.mdx b/snippets/supabase-database-connection.mdx index b7a502e4..02af498b 100644 --- a/snippets/supabase-database-connection.mdx +++ b/snippets/supabase-database-connection.mdx @@ -18,7 +18,8 @@ 2. Click **"Test Connection"** and fix any errors. -3. Under the **"Client Auth"** tab, enable **"Use Supabase Auth"** and enter your Supabase **JWT Secret**: +3. Under the **"Client Auth"** tab, enable **"Use Supabase Auth"** and enter your Supabase **JWT Secret**: + ![](/images/authentication/use-supabase-auth.png) From 2f59c715bef8d6fdb149c11f7040f2de717ab5a4 Mon Sep 17 00:00:00 2001 From: benitav Date: Thu, 5 Dec 2024 09:22:37 +0200 Subject: [PATCH 3/3] Fix images --- installation/authentication-setup/supabase-auth.mdx | 4 ++-- snippets/supabase-database-connection.mdx | 11 +++++++---- 2 files changed, 9 insertions(+), 6 deletions(-) diff --git a/installation/authentication-setup/supabase-auth.mdx b/installation/authentication-setup/supabase-auth.mdx index 716cb0e4..81a830be 100644 --- a/installation/authentication-setup/supabase-auth.mdx +++ b/installation/authentication-setup/supabase-auth.mdx @@ -36,11 +36,11 @@ To implement either **Supabase Auth** or **Anonymous Sign-Ins**, enable the rele 2. Under the **"Client Auth"** tab, enable **"Use Supabase Auth"** and enter your Supabase **JWT Secret** (the secret can be copied from your Supabase project's API Settings): - ![](/images/authentication/supabase-jwt-secret.png) + - ![](/images/authentication/use-supabase-auth.png) + 3. Click **"Save and deploy"** to deploy the updates to your instance. diff --git a/snippets/supabase-database-connection.mdx b/snippets/supabase-database-connection.mdx index 02af498b..c48c8dc4 100644 --- a/snippets/supabase-database-connection.mdx +++ b/snippets/supabase-database-connection.mdx @@ -1,4 +1,6 @@ -1. Copy the database connection details from Supabase: +1. Copy the database connection details from Supabase: + + @@ -19,9 +21,10 @@ 2. Click **"Test Connection"** and fix any errors. 3. Under the **"Client Auth"** tab, enable **"Use Supabase Auth"** and enter your Supabase **JWT Secret**: - - ![](/images/authentication/use-supabase-auth.png) - + + + + 4. Click **"Save and deploy"** to deploy the updates to your instance.