git rev-parse HEAD returns aa116e6b4d2f42731729db01f28875494988a684
I've looked through the Chrome dev console in the network section and it seems that ajaxify is receiving 304: Not modified responses, and gets stuck on opacity:0. A very weird functionality. All of the elements are loaded in, but they are all invisible. Very odd.
There is an Uncaught Error: Mismatched anonymous define() module error that occurs on page load in ajaxify.
Okay, I guess never mind. One of the external sources I was including was causing the problem. I removed the define call and now it's working.
The recommended method of sharing sessions between two separate and distinct applications is through OAuth2. We recommend this approach because NodeBB maintains its own user records, so that we can keep track of user-related metrics and other data. Relying on another database would be tricky, prone to breaking, and quite possibly dangerous.
Luckily, it's quite straightforward to get things working with OAuth2!
The first step is getting your application to expose an OAuth2 endpoint. If you're running a Node.js based app, you can use a module called OAuth2orize.
Once that is set up, you'll want to take a look at the SSO plugin skeleton for customised OAuth deployments -- nodebb-plugin-sso-oauth. You'll take this plugin, fork it, and modify it to communicate with your OAuth endpoint.
Once everything is working properly, you should be able to register and log in/out via your web app.