Tag Archives: idno

Posted on
by

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!

Posted on
by

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.

Known Dev Scripts

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 --dev

Console Tools

Next 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 --dev

It goes without saying that these should not be installed on a production system – with great power, and all that.

Enjoy!

» Visit the project on Github...

Posted on
by

Recently, the Composer Installers project added support for Known, which opened up the exciting possibility of using Composer to deliver Known plugins and Themes.

Those of you who are tracking GitHub, you might have noticed that all the plugins and themes have disappeared!

Fear not, however. They are now all in their own repositories and installable via composer.

This is pretty cool, as not only does this solve some of the distribution and directory naming issues we were having (since now, composer manages both the downloading and making sure the plugin is installed to the correct location), but it also makes it super easy to role custom builds of Known with just a change to one file!

Having the plugins in their own repos will also hopefully make it much less daunting for people to get involved with development.

I’ve written before how package authors can update their stuff to take advantage of this, but I’ve already updated most of the core plugins and themes.

Enjoy!