rorysaur/quack

user can register / sign in by providing their username (create if it doesn't exist)

Opened this issue · 4 comments

...and messages are stored with the username, and displayed with the user's display name.

we can hold off on requiring a password if it will be a lot more complex.

I see Firebase provides email & password-based auth out-of-the-box: https://www.firebase.com/docs/web/guide/login/password.html

Does anyone foresee any issues using it? We could roll our own auth of course but that seems overkill since, you know, this project is mainly about React. Thoughts?

we were planning to use firebase auth. go for it.

Firebase is no more. We should roll our own with Phoenix.

✅ add email/password fields to user model
✅ registration UI
🔲 registration backend
🔲 sessions controller
🔲 authenticate on routes; redirect to login
🔲 success/error messages
🔲 stylez