Varnish config on Debian
I’ve just spent too long being very confused as to why varnish wasn’t working
I’d forgotten that the Debian version doesn’t read the default.vcl config file by default!
You ha
Technical information on this site may be out of date : no updates since 2015
I’ve just spent too long being very confused as to why varnish wasn’t working
I’d forgotten that the Debian version doesn’t read the default.vcl config file by default!
You ha
In order to make releases repeatable, to be able to test updates and share work will colleagues it is really useful to install new modules (and disable old ones) in update hooks.
This way one just has to update the code, then run update.php and you have the latest version of the site.
I’m using varnish to cache a REST service that’s slow enough to cause me grief in development.
Out of the box it assumes you are caching your own server and that the client is already using the right host header.
To specify that it should use a host header to match the backend I’m using a config like
To make a Drupal module that provides triggers you need to
When I installed my system I wasn’t quite happy with the way the installer divided my hard disk - but at the time I was in a hurry…
I have since found that repeated loading of databases during development used up all available space in /var and debug files were filling /tmp
So I had to figure out how to resize them.
For several years I worked as a web developer for the Ramblers and this experience very much colours my view of todays release of free maps and postcode data.
This is a fantastic and significant step in the direction of ensuring that some of the worlds best mapping assets do the most good for society as a whole.
I need a user hook that sends password reset events.
I created a very simple module to do this - but it doesn’t work.
I just found out the painful way that if you manually update a column which is normally calculated automatically as an auto_increment it seems to work at first ..
but MySQL doesn’t update the auto_increment value for the table - so subsequent inserts can fail.
I’ve long been puzzled by the official advice on upgrading Drupal
It basically says you should delete everything, unpack a new Drupal version, and replace your customisations.
I like to use version control to manage my site.
Here’s a basic Drupal Module that pulls CKAN data into Drupal.
It provides a simple search interface - when the user views a CKAN package for the first time a corresponding node is created.