rix1 / auth-now Goto Github PK

Storage is planned to be a simple, generic key-value storage that returns json. /api/data/<id> should return the (json) value from the key <id>.

Alternatives:

• S3, where key = "filename" and value is its content
• Firebase.

@andrroy and me talked briefly about it yesterday. We're both noobs in Firebase, and want to learn. So we're leaning towards that.

There's dummy storage code in api/data/[id].js.

Add ability to change the content of /api/data/<id>

No testing library added yet.

• Add test library
• Add tests for auth.js
• Add tests for email.js
• Add tests for /api/data
• Add tests for /api/auth (#5 will probably lead to extra endpoint here)

Endpoints /api/sendgrid/send/<mail> and /api/mailgun/send/<mail> have different behavior

• sendgrid sends html, mailgun sends plain text. Send html with both?
• sendgrid html mail does not contain the same text as its text version.
• sendgrid allows for setting subject and text via GET param. Remove and use content that mailgun uses?
• Extract sendgrid and mailgun code to a library, and replace api endpoints with /api/email/login/<email>?

It would be really cool to experiment with TensorFlow and face detection to see if we could come up with a endpoint like auth-now.sh/api/face 😅

Problem: You have an old session on your computer in an old tab. When opening it, and performing an action, you overwrite newer data.

Suggested solution: Reload your local data if your local version is older than the one stored at the server

Check out the following project, looks like something we could use: https://github.com/chromakode/react-html-email

The purpose of the */send endpoints is to send a secret login link to the email.
It should not expose the secret link as a response.

Related: #5

We're currently missing information on how to run the application with the new JWT setup. In addition we're missing info on how to set secrets in the production environment.