Closed amj closed 8 years ago
I repro'd; no trace of the error in logs... gotta figure out how to get gunicorn to actually log the stack traces for a 500.
Didn't add the api key to the dev box's .env file, so the MM endpoint redirected me to login.
Fixed the original issues.
note to self: User linking flow is still broken; looks like there's some issues with app vs. current_app and using the extensions (this changed when I started using this pattern http://flask.pocoo.org/docs/0.10/patterns/appfactories/)
current_app stuff got fixed; waiting on an official email address to send email from
What sort of information do you need to send email?
I mentioned this briefly to @amj
I'll need the email server host name (eg SMTP.google.com) and username/password (eg online-ratings@usgo.org /password )
Will this only be sending out email? no expectation of reply back? Will it need to read from a mailbox?
Hmm. Managing an email inbox could get annoying, I think. We can make it no reply and add a link to the online ratings github issues page in the footer of the email.
AGA ID workflow is confirmed working, except you have to add manually add :8080 to all the URLs that are part of the flow, at the moment. That should work properly on prod when we get there.
steps to repro: