Fix localhost:3000 links (#1125)

lucia-auth · Sep 15, 2023 · 67870cd · 67870cd
1 parent 349c696
commit 67870cd
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/documentation/content/guidebook/github-oauth-native/electron.md b/documentation/content/guidebook/github-oauth-native/electron.md
@@ -3,7 +3,7 @@ title: "Github OAuth in Electron"
 description: "Learn how to implement Github OAuth in Electron desktop applications"
 ---
 
-> These guides are not beginner friendly and do not cover the basics of Lucia. We recommend reading the [Github OAuth](http://localhost:3000/guidebook/github-oauth) guide for regular websites first.
+> These guides are not beginner friendly and do not cover the basics of Lucia. We recommend reading the [Github OAuth](/guidebook/github-oauth) guide for regular websites first.
 
 We'll be using bearer tokens instead of cookies to validate users. For the most part, authenticating the user is identical to regular web applications. The user is redirected to Github, then back to your server with a `code`, which is then exchanged for an access token, and a new user/session is created.
 

diff --git a/documentation/content/guidebook/github-oauth-native/expo.md b/documentation/content/guidebook/github-oauth-native/expo.md
@@ -3,7 +3,7 @@ title: "Github OAuth in Expo"
 description: "Learn how to implement Github OAuth in Expo mobile applications"
 ---
 
-> These guides are not beginner friendly and do not cover the basics of Lucia. We recommend reading the [Github OAuth](http://localhost:3000/guidebook/github-oauth) guide for regular websites first.
+> These guides are not beginner friendly and do not cover the basics of Lucia. We recommend reading the [Github OAuth](/guidebook/github-oauth) guide for regular websites first.
 
 We'll be using bearer tokens instead of cookies to validate users. For the most part, authenticating the user is identical to regular web applications. The user is redirected to Github, then back to your server with a `code`, which is then exchanged for an access token, and a new user/session is created.
 

diff --git a/documentation/content/guidebook/github-oauth-native/tauri.md b/documentation/content/guidebook/github-oauth-native/tauri.md
@@ -3,7 +3,7 @@ title: "Github OAuth in Tauri"
 description: "Learn how to implement Github OAuth in Tauri desktop applications"
 ---
 
-> These guides are not beginner friendly and do not cover the basics of Lucia. We recommend reading the [Github OAuth](http://localhost:3000/guidebook/github-oauth) guide for regular websites first.
+> These guides are not beginner friendly and do not cover the basics of Lucia. We recommend reading the [Github OAuth](/guidebook/github-oauth) guide for regular websites first.
 
 We'll be using bearer tokens instead of cookies to validate users. For the most part, authenticating the user is identical to regular web applications. The user is redirected to Github, then back to your server with a `code`, which is then exchanged for an access token, and a new user/session is created. The hard part is sending the session token (ie. session id) from the server back to our application.