-
-
Notifications
You must be signed in to change notification settings - Fork 5
Login-by-email feature and supporting infrastructure #23
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.
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
Conversation
…nd add user registration logic
…oteBlockWorld into feature/login-by-email
…remove forRoot method
…e useFactory for configuration values
|
Just a reminder
|
… template inclusion
…pdating button styles
…mprove email context handling
…for improved rate limiting
…k for Axios errors
|
Thanks for implementing these changes! The email template looks great now. I'll still review the frontend and likely do some small changes, though I'm only able to do that after about the 22nd this month. Let me know when you're done with your changes :) |
…nto feature/login-by-email
|
This PR is waiting on us setting up an email server to be merged. :) |
I feel it would be good to merge and maybe disable the email server-related feature until it's available. |
…nto feature/login-by-email



This pull request implements email-based authentication and adds necessary supporting services and infrastructure.
Authentication & Email Features:
passport-magic-loginMagicLinkEmailStrategyfor email authenticationMailServicefor SMTP email handlingInfrastructure Updates:
EnvironmentVariableswith new configs and validationTechnical Improvements:
useFactoryandinject(Nest.js upgrade compatibility)Documentation Updates:
CONTRIBUTING.md: The setup instructions have been updated to usedocker-compose-dev.ymlinstead ofdocker-compose.yml. Additional environment variables and detailed setup instructions for both the backend and frontend have been added. New sections for running only the backend or frontend, populating the database with test data, and running tests have been included.