Darren shared some of the problems which had appeared on the Open University TU100 My digital life forums relating to the SenseSense programming language which the Open University have developed from Scratch for use with mature students. Darren himself had had a problem because his 64-bit OS was just that; it had no 32-bit libraries.
Kriss and Shi Then shared their experiences of automating the development of static websites. Their first attempt was a ‘bootstrap’ CMS using App Engine and text files as input to generate the code which was tried out among the gaming community.
But they decided to step away from this in part because App Engine is aimed at large scale installations.
Their second attempt was ‘pancake’ using Open Resty which runs LuaJIT in Nginx to take advantage of Nginx’s efficiency. It was modular, used chunks and allowed multiple CSS files to enable different layouts within a website.
From this they moved on to ‘pated’ which has some similarities with Jekyll and decided to use the hat character as part of their naming convention; a directory starts with a hat character and file has one somewhere in its name. They illustrated that you can do quite a bit with static websites by demonstrating one showing aid data.
In practice, organising the data is the hardest part; the chunks are all in JSON format and you could use those on a dynamic website.
David C then gave us a running commentary on automating kernel security patches (of which there has recently been a rash) at Slackbuilds.
The idea is to have a single system that will notice patches to the stable kernel and apply them to Slackbuilds in such a way that builds will be reproducible, that is, however many people build it, all builds will be bit identical.
It needs something to read the RSS feed and apply
grep — in other words, a BASH script! This needs to prompt the router to wake up in order to start building the new kernel.
As he wants something simple, [If This Then That]](https://ifttt.com/) and Lighttpd on the router would seem to do the trick, though it was suggested he might want to consider Huginn instead of IFTTT.
This led into a discussion of the possibility of using a Twitter feed rather than RSS, in which case you would need to use https: with a single referer, and the availability of really cheap web servers.