Will Vincent

So I previously blogged about replicating Meteor's password hashing, so that migration off of meteor could be (somewhat) painless. While I had it working for JWT logins with Persona in my code, I couldn't get it working with basic auth.
I have some paths that serve up static files (swagger documentation and so forth) for internal consumption only, so I have a middleware that checks for the existence of a flag indicating if a user is an 'internal' user or not, and then I also attached...

I don't know off hand if there will be more posts, but the potential seems likely, so we'll just go ahead and call this installment #1.
I'm in the process of rearchitecting the data layer of an application that we have in production presently that's been cobbled together by a variety of people, some with a high probability of questionable competency, over several years... It's the classic...

It seems a fairly common pattern I encounter in Node-based codebases is an index.js file that simply imports a bunch of other files, and then exports them all in an object to be consumed elsewhere by simply requiring the directory that index file lives...

As you may have read previously, when doing some routine maintenance and attempting to finally crack down on all the SPAM that was hitting my inbox, I managed to hose the email stack pretty thoroughly.
I'm sure I could have recovered from it, but it'd been so long since I'd done much maintenance on the system that it seemed like a good time to just go ahead and rebuild from scratch....