4 ms·
We had a bug in email validation (worked on staging grumble grumble). Separately, our deploy script blows away memcached. Guess where email validation tokens
by patio11 11y ago
We had a bug in email validation (worked on staging grumble grumble). Separately, our deploy script blows away memcached. Guess where email validation tokens were kept.
I temporarily turned off bust-cache-on-deploy and the rapidly rising number of validated emails suggests things are working now. Now back to more DevOps craziness.
- laarc 11y agoI wanted to give you a status update of what new users currently experience. Or at least what I'm experiencing. After creating an account, I was redirected to the front page with no notification about whether it succeeded or failed. No emails have arrived. When I try to create it again, I get "username already taken" and "email already taken", so something worked. But when I try to log in, I'm redirected to the front page with no notifications. In other words, login is failing. To clarify, this isn't a complaint. Congratulations on launching, and apologies if you're already aware of these issues. Edit: This is similar to https://news.ycombinator.com/item?id=10724699 https://news.ycombinator.com/item?id=10724699 but I'm unable to log in after clearing cookies. I get "Couldn't sign in. Check username/password" for a correct password.
- Alex3917 11y agoFor email validation you can also just used a signed json token (jwt), so that way the only thing you need to store on your servers is the secret key.