Just a quick one.
I’ve been playing about with Node.js some more, and very quickly (alarmingly quickly) hacked together a very simple Node library for talking to the Known API.
The main.js has an example where I will post a status update, but obviously other updates are possible.
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.
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
Known allows you to install Known via the command line, this can be handy for scripted installs, using non-MySQL database backends, or when installing over a terminal connection to a remote server.
Go in to /warmup/CLI, and you’ll see CLIInstaller.
To install a brand new Known using an interactive install simply run
./CLIInstaller install
A manifest is used to pass configuration options to the CLI installer so that you won’t be prompted for them. This is useful for scripting installs.
First, generate a manifest template:
./CLIInstaller generate-manifest /path/to/manifest
Next, edit that file and fill in the appropriate option.
Now, you are able to pass these options to the installer:
./CLIInstaller install config.ini /path/to/manifest
You’ll also notice I’m specifying the config.ini ini file to write to, you can write this config to other files as necessary, which is handy if you’re using per-domain configuration.
The CLI installer has a few other options that might be useful:
If you just want to check that your server has the necessary requirements to run Known, you can execute:
./CLIInstaller.php check-requirements
If you want to generate a config file, but without going through the full install (useful if you want to generate a new domain config in a script), you can use the following command to do so
./CLIInstaller.php makeconfig /path/to/manifest
This will output the new config to stdOut. You can save it to an ini file as appropriate.