Skip to content

Open-source status page, incident response and uptime monitoring

add docs on the type of providers for auth (#225)

Kelvin Amoaba34f6f97e9ba0
diff --git a/apps/docs/pages/get-started/setup-env.mdx b/apps/docs/pages/get-started/setup-env.mdx
index c4ad4fead..566c1dae6 100644
--- a/apps/docs/pages/get-started/setup-env.mdx
+++ b/apps/docs/pages/get-started/setup-env.mdx
@@ -11,17 +11,23 @@ to Cleark Auth.
create a new account if you don't have one yet.
2. Once logged in, go to your dashboard at
- [https://dashboard.clerk.com/](https://dashboard.clerk.com/) and create a new
- app if you haven't already.
+ [https://dashboard.clerk.com/](https://dashboard.clerk.com/) and select
+ create a new app if you do not have any application already.
-3. After setting up your app minimally, navigate to the "DEVELOPERS" section in
- the left-hand menu and find "API Keys."
+3. On the create new app screen, enter your app name and select **Google** and
+ or **GitHub** under the section _How will your users sign in?_
-4. In the "Quick Copy" section, make sure that Next.js is selected, then click
+ > Please note that using other providers will cause issues in the application
+ > due to the different payload received from Clerk.
+
+4. After setting up your app, navigate to the "DEVELOPERS" section in the
+ left-hand menu and find "API Keys."
+
+5. In the "Quick Copy" section, make sure that Next.js is selected, then click
the copy icon to obtain the keys. Copy the values for
"NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY" and "CLERK_SECRET_KEY."
-5. Paste these values into the `.env` file under their respective variables. It
+6. Paste these values into the `.env` file under their respective variables. It
should look something like this (real values without censorship):
```