Skip to content

docs: clarify Google OAuth environment variable placement for frontend and backend #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Mohit-001-hash wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: clarify Google OAuth environment variable placement for frontend and backend #49

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,10 +36,11 @@ A full-stack application designed to track your Data Structures and Algorithms (

### Backend Setup
1. Ensure PostgreSQL is running and update your database credentials in `src/main/resources/application.properties` or `application.yml`.
2. For Google login, create a Google OAuth web client and set the same client ID in both runtimes:
```bash
2. For Google login, create a Google OAuth web client and configure the client ID in both runtimes:

**Backend:** Add this to your `src/main/resources/application.properties` (or `application.yml`):
```properties
GOOGLE_CLIENT_ID=your-google-web-client-id
VITE_GOOGLE_CLIENT_ID=your-google-web-client-id
```
The backend verifies the Google ID token audience with `GOOGLE_CLIENT_ID`; no Google client secret is required for the browser button flow.
3. Build and run the backend using the provided Maven wrapper:
Expand Down