This only ensures that the e-mail is valid and exists, right? It doesn’t proof that the person registering is the owner of the email account.
antalvarenga
antalvarenga
idi527
I wouldn’t put short-lived data into a database, I would store it either in a process or an ets table with some kind of time-to-llive, probably Process.send_after(self(), {:clean, verify_token}, @ttl).
2
bobbypriambodo
antalvarenga
Haven’t reached that part of the book yet :p. Isn’t there some package to handle that confirmation flow?
1
idi527
I don’t know if there is a package for it, but I can try and outline the code needed for this flow if you want. It’s not that difficult …
1
antalvarenga
idi527
https://github.com/idi-ot/mailer
I’ll refactor it later though. If you have any questions, I’m happy to answer.
It’s just a stock phoenix 1.3 app right now.
The important bits are:
EDIT: Refactored it a little. Now it’s an umbrella project. Need to put send_verification into ecto multi.
2
OvermindDL1
I’d definitely put it in the database! They may not get around to checking their email soon and the server could restart before then! o.O
8
antalvarenga
For the record, here’s how I’ve done it.
To send emails, I used the mailgun package. The setup is described in the phoenix docs section “Sending Email with Mailgun”
To add the confirmation logic, I started a new phoenix application with phauxth (with mix phauxth.new --confirm), which is the openmaize library for Phoenix 1.3, just to see the code and to test it. Then I installed the phauxth package to my ongoing project and replicated the code needed just for the confirmation flow.
Thank you all for all the help!
0