Supabase Auth #12

[Ellahinator]

Addresses the following issue:

• 12

This PR introduces authentication actions and middleware for Supabase, including Google OAuth and basic email/password authentication.

Setup Instructions:

Must Do:

1. Copy .env.local.example into .env.local and set up the following environment variables:

NEXT_PUBLIC_SUPABASE_URL=<your_supabase_project_url>
NEXT_PUBLIC_SUPABASE_ANON_KEY=<your_supabase_anon_key>
NEXT_PUBLIC_REDIRECT_URL=http://localhost:3000 # or the production URL

2. To get Google OAuth working, please follow this guide: Supabase Google Signup

TODO:

• [x] Add sign-in button on the web page
  • https://github.com/trypear/pear-landing-page/pull/20/commits/9f25f93af0bad1049eb6240cdbd50221e46895a0
  • if signed in, it shows Dashboard, subject to change
• [x] Implement reset password functionality
• [ ] Make "keep me signed in" work
• [ ] #21 we need to use a custom SMTP server in prod: Email Templates
• better error handling
• ?Implement auth-protected routes
• ?Add more paths to exclude from middleware.ts (routes that don't access Supabase)
• PRIORITY for backend: Populate users table for new users: Managing User Data

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
pear-landing-page	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 9, 2024 5:34pm

[Ellahinator]

need to fix redirectTo not working with Google signing. fixed: https://github.com/trypear/pear-landing-page/pull/20/commits/ac58ced0ec2660cd018efd3496a16d69417f4b56

[shrix1]

Hey, @Fryingpannn @nang-dev ,Supabase email SMTP is super bad (PRO plan also 10-20 email only). So, we can use Resend SMTP for auth OTP verification and Welcome email and other stuffs.

check the Pricing below :

[shrix1]

Hey, Nice work @Ellahinator Im working on adding Custom SMTP Issue : https://github.com/trypear/pear-landing-page/issues/21

[Ellahinator]

We can merge this by having 2 extra things Logout button working Feature flag checking to only show the buttons if on local (we don't want this in prod yet as not fully complete, but can merge current pr first)

These two have been implemented.

Whats left that should be prioritized is

• Populate users table for new users: Managing User Data

  Other than that, I think this is ready to merge for now.

[Fryingpannn]

FYI

https://discord.com/channels/1237009981803462729/1247633935748435990/1249112511882465382

Confirmed with @ItWasEnder regarding user data flow, who is working on creating the db schema for a custom user table.

When users sign up, their info is stored in the default auth schema's users table (the one automatically linked with the supabase auth). We have a database trigger which will then automatically also insert these new users in our custom user table.

This custom user table is where we will perform reads from. I think this is also what you're referring to in the Managing User Data link you mentioned.

[Fryingpannn]

Solve merge conflict and we can merge! Good shiet 👏

[Ellahinator]

Should be good to merge @Fryingpannn