So far we only had sign up/sign in via GitHub. With this PR we are
adding email sign up/sign.
I started using Supabase Auth UI, because there is starting to be a lot
of auth UI we would need to handle (having auth inputs, choosing between
different providers, sign up flow…) and we can get it for free now.
What is missing:
- [x] Testing with GH — I think I configured it correctly, but haven’t
tested it yet
- [x] Customize style of the supabase auth ui (it should be possible to
override anything) to match our docs style
- [x] Decide if we want to put the auth ui on a completely separate page
(we may have to move the app router layout?)
- [x] Make sure the sign up and sign in buttons flow still makes sense
and works — sign up should redirect to the actual sign up version of the
auth ui, but the #auth-sign-up that should be used seems not to be
working correctly with router.push yet :thinking_face:
- [x] Fix redirecting to the same url (test in prod)
- [x] Fix redirecting to sign up
- [ ] _Customize Supabase auth emails, confirm email_
- [ ] _Styling of "confirmation email" and "wrong password"
announcements_
- [ ] _Enable reset password again_
- [x] Redirect on confirmation email
- [x] Set SMTP
- [x] Check if all the analytics are still in correct place
- [x] Fix hydration errors
- [ ] _Test signing in with the same email for another existing account
created via GitHub_
- [x] Make auth urls more readable
- [x] Check if pathnames are correctly encoded
Tomas Valenta