[REQ] Registration

[djzara]

Describe the requirement Just your run of the mill registration system. Nothing super complex. Use email verfication.

• registration evo, model, and repository
• track email signed up with, verification status, expired status (maybe in lieu of?), ip, location of that ip at that time, user agent, registration token
• consider adding something that checks periodically to see if the registration has expired and flag it to help save some checks on occasion. easier to check a flag than do some date math every single time we let a user register
• needs to hook up to SES <- put this behind some kind of mailer interface though, I don't want to bind us to AWS
• add a mail template
• when a user signs up, they get an entry in users and one in registrations. the user cannot login as long as the registration entry is not validated.
• if a user tries to login and is not validated, take them to the "resend verification" page (and build one)
• if the registration expires, the user MUST generate a new token. add a new row instead of reusing the old one. One token per registration session. If they want a new token they have to click to get one...needs to not allow spamming.

What is the value added? You can use the site

Are additional resources or packages needed? Decide on what we'll use to hash passwords, what min requires should be, and how much information we really need.

Should we allow registration via other services like Apple and Google? something to think about

[djzara]

Some of this stuff isn't needed anymore once this was migrated to Laravel, updated thusly:

registrations model, repo, migration

track email signed up with, verification status, expired status (maybe in lieu of?), ip, location of that ip at that time, user agent, registration token
consider adding something that checks periodically to see if the registration has expired and flag it to help save some checks on occasion. easier to check a flag than do some date math every single time we let a user register
add a mail template
when a user signs up, they get an entry in users and one in registrations. the user cannot login as long as the registration entry is not validated.
if a user tries to login and is not validated, take them to the "resend verification" page (and build one)
if the registration expires, the user MUST generate a new token. add a new row instead of reusing the old one. One token per registration session. If they want a new token they have to click to get one...needs to not allow spamming.

I don't really like using too much out of the box stuff, but a lot of the registration stuff is definitely already there