Follow this guide together with the guide on Supabase to setup Launch Leopard with Supabase. https://supabase.com/docs/guides/auth/server-side/sveltekit

Make sure to follow Step 8 as well in the Supabase guide to setup the email auth template correctly.

​
Setting up the Supabase boilerplate

  1. Go to Supabase and create an account.
  2. Once you have created an account, create a new project.
  3. Once you have created a project, go to the project settings and go to Project Settings > API and copy the URL, anon public API key to your .env file.
  4. Then go to Project Settings > Database and copy the Nodejs Connection string to your .env file (make sure to replace [YOUR-PASSWORD] with your password).
.env
PUBLIC_SUPABASE_URL="YOUR_SUPABASE_URL"
PUBLIC_SUPABASE_ANON_KEY="YOUR_SUPABASE_KEY"
PRIVATE_DATABASE_URL="YOUR_DATABASE_URL"
PRIVATE_SUPABASE_SERVICE_ROLE_API_KEY="SECRET_ROLE_KEY"

The PRIVATE_SUPABASE_SERVICE_ROLE_API_KEY is used to bypass the Row Level Security policies. This is used for Stripe webhooks, since they don’t have a user context. Make sure to keep this key secret, and don’t share it with anyone.

​
Setting up the database

Add a profile table to your database with the following SQL:

This will also create a trigger that will automatically create a profile for every new user.

create table public.profiles (
  id uuid not null references auth.users on delete cascade,
  first_name text,
  last_name text,
  stripe_customer_id varchar(255),
  subscription varchar(255),
  primary key (id)
);

alter table public.profiles enable row level security;
-- Create a policy that allows users to update only their own profiles
CREATE POLICY update_own_profile ON public.profiles
    FOR UPDATE
    USING (auth.uid() = id);

-- Create a policy that allows users to view only their own profile
CREATE POLICY select_own_profile ON public.profiles
    FOR SELECT
    USING (auth.uid() = id);

-- inserts a row into public.profiles
create function public.handle_new_user()
returns trigger
language plpgsql
security definer set search_path = public
as $$
begin
  insert into public.profiles (id)
  values (new.id);
  return new;
end;
$$;

-- trigger the function every time a user is created
create trigger on_auth_user_created
  after insert on auth.users
  for each row execute procedure public.handle_new_user();

Already have users but didn’t setup a profiles table? Run this SQL to create profiles for them:

INSERT INTO public.profiles (id)
SELECT u.id
FROM auth.users u
LEFT JOIN public.profiles p ON u.id = p.id
WHERE p.id IS NULL;
Auth.js One time payment