Well, the clocks have gone back, and the nights are drawing in. If you’re anything like me, this means you just want to find somewhere warm to curl up in until spring.
But before you do, I would just like to point you to the fact that Known 1.0 is finally out of the door!
It’s been a long journey to get to this point, but I’m delighted to finally get to a point where we can draw a line in the sand.
Crack open the beverage of your choice, and go download Known 1.0 now!
Just a quick update…
In the run up to the Known 1.0 release, I’ve made a small tweak to the back end caching objects. Essentially, they functionally work the same, but are implemented using symfony cache components.
Further down the line I’m thinking about replacing our cache entirely with symfony in order to allow for easier caching back ends, not to mention the far superior “cache contract” interface.
This is a low level thing, but useful if you’re a plugin developer to know what is coming down the pipe!
A few of you have been asking about some of the Known dev tools that I use.
Well, I’ve been writing them as I go, and they’re a little bit dotted around, but since moving to composer I’ve been trying to link them up a bit.
The main dev scripts that I’ve been using are here. Requiring this package will also fetch the language tools scripts and the PHPCS code formatter config.
All of these are already included in the Known checkout in the vendor directory, if you’re checking out from git, and composer installing the dev dependencies (default).
composer require mapkyca/known-dev-scripts --devNext are a set of console tools that I’ve built up over time which give me some ability to nudge data around, and to get various dumps of raw data.
They’re dotted around in their own repos, and can be installed individually, but for convenience you can grab them all in one go:
composer require mapkyca/known-console-tools --devIt goes without saying that these should not be installed on a production system – with great power, and all that.
Enjoy!