From 98c4b5f21848f5a61f3bce38bf70aba9064fe97d Mon Sep 17 00:00:00 2001
From: Evan Unit Lim <62005952+evlim@users.noreply.github.com>
Date: Thu, 15 Aug 2024 01:28:15 +0800
Subject: [PATCH] Match file name

login_config.ts
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index cd95409a..fbcfab31 100644
--- a/README.md
+++ b/README.md
@@ -212,7 +212,7 @@ Finally: if you find build, formatting or linting rules too tedious, you can dis
   - Test that the "sign up" and "forgot password" emails link back to your domain correctly by checking the have a redirect_to parameter to your `yourdomain.com/auth/callback`. If they link to the base URL or another page, double check you have the config above set correctly.
 - OAuth Logins
   - Decide which oauth logins you want to support, and set them up in the Supabase Auth console under “Auth Providers”. Be sure to provide them the Supabase callback URL. Also be sure to set any platform specific permissions/settings to retrieve their email as part of the login (for example, for Github it's under `Account Permissions > Email Address > Read Only Access`
-  - Edit `oauthProviders` list in `/src/routes/(marketing)/login/login_conf.ts` with the list of providers you chose. If you don’t want any OAuth options, make this an empty array.
+  - Edit `oauthProviders` list in `/src/routes/(marketing)/login/login_config.ts` with the list of providers you chose. If you don’t want any OAuth options, make this an empty array.
   - Test each provider to ensure you setup the client ID, client secret and callback correctly for each
 - Auth Email SMTP
   - Supabase has a limit of 4 emails per hour on their development server. You should [Configure a Custom SMTP](https://supabase.com/docs/guides/auth/auth-smtp) sending emails from your own domain.