express-objection-starter
express-objection-starter copied to clipboard
JaneJeon
an opinionated, production-ready, isomorphic express/knex/objection starter with centralized configuration
For example, the password reset/verify endpoints should be limited more severely than others, like maybe 3 per day. Perhaps using express-unless?
https://github.com/auth0/node-jsonwebtoken with JWT calls https://github.com/ai/nanoid/tree/master/async with any secure id generation
https://github.com/tj/connect-redis/blob/master/migration-to-v4.md Related: #10
using https://github.com/jaredhanson/connect-ensure-login instead of `requireAuthN`
https://github.com/vinialbano/passport-magic-link#readme
Find a way to automatically convert _all_ time values into milliseconds using https://github.com/zeit/ms so that I can write `1 day` instead of `86400000` (yuck). The challenge will be figuring out...
Ensure that email connection works, and that the services are connected to redis and to the primary data store. Only if those pass without problem, _then_ the server should be...
It'd be ideal if we could just assume that the server is running in a vacuum where the _only_ thing it needs to do is to handle req/res cycles. But...