Fix#3 : Implement Firebase authentication with domain validation #46
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chore: pr checking frontend
refactor part of bsoc-bitbyte#2: add folder structure
…dler and apiReponse logic
…or-final Fix bsoc-bitbyte#17: refactored the backend structure and applied apiResponse and asyncHandling throughout the project
fix: Bug fix uploading and deleting and naming upload files
…entation [docs] bsoc-bitbyte#21 : update readme and setup file
fix bsoc-bitbyte#42: fix package.json and updated package-lock accordingly
- added revised header and footer designs as per figma - added sems and branches - removed user stories for a cleaner design and ux Closes bsoc-bitbyte#12
Author
|
@ritankarsaha @harshiill please review I have not made the route protection part |
Fix bsoc-bitbyte#33: Updated docs for .env configuration wrt cloudinary
…boarding Fix bsoc-bitbyte#12: added a home/ user onboarding page
Collaborator
|
@ShirshenduR pls fix conflcits and push a new commit, take care of linting errors too but that's okay, not a biggie, just go through commit message patterns you will get it. Fix the conflicts. Also I need a demo or a proof of work to begin reviewing. |
ritankarsaha
requested changes
Jul 24, 2025
backend/.env.sample
Outdated
Comment on lines
8
to
9
|
|
||
| CLOUDINARY_URL=cloudinary://<your_api_key>:<your_api_secret>@<product_environment_name> | ||
| CLOUDINARY_PUBLIC_ID=<product_environment_name> | ||
| CLOUDINARY_PUBLIC_ID=<product_environment_name> |
backend/.env.test
Outdated
Comment on lines
14
to
16
| # Firebase Configuration | ||
| FIREBASE_PROJECT_ID=<your_firebase_project_id> | ||
| FIREBASE_SERVICE_ACCOUNT_KEY_PATH=<your_firebase_service_account_key_path> |
Collaborator
There was a problem hiding this comment.
pls make updates in the doc or readme as well if they have sample env structure.
Collaborator
|
@ShirshenduR i need to review this in detail, an important PR. WIll do tomorrow. Good work ! |
fix(auth): Made auth using firebase and domain restriction fix: auth feat: added auth
Author
Screen.Recording.2025-07-25.at.5.01.32.AM.mov |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
11 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
In this PR I have added firebase auth for and login for both via registering and also by google sign in. Add the Exam-bud-firebase.json from Firebase console and setup both frontend and backend envs
Essential Checklist
Proof that changes are correct
PR Pointers