Just another quick update…

In an ongoing effort to make use of the Known API easier and more flexible, the latest version available in GitHub, or via my unofficial packages, now has built in support for OAuth2.

OAuth2 server functionality is provided by an updated version of my OAuth2 Server code, which I’ve written a bit about before.

Going forward, I’m hoping to build out an easier way for third party clients to be able to connect, paving the way for a possible mobile client.

Anyway, go grab the latest version and have a play!

So, Node is becoming more and more a requirement for doing modern dev work. I admit I’ve been slow on the uptake on this, but I’m always wanting to learn new things, so I’ve been getting to grips with it recently.

Spoiler alert: it’s really really easy if you’re coming from a bit of a web background and have written a bit of frontend javascript.

So, in part to build up a bit of node code on my github profile, and in part to prove a concept for something I talked about recently when I rewrote the Known event queue processor back end, I wrote a Node version of the event queue processor service.

Usage

Configure your database settings and path to Known in the package.json.

By default, the settings are configured to talk to Known as installed with by the vagrant package.

Then, run the event queue:

node main.js

» Visit the project on Github...