I usually manage website deployment with bash scripts that run remote commands on the servers

In order that I can see what is going on and debug any errors verbose output is useful.

Running “bash -ex” causes each line to be output as it progresses and halt on any error so that you don’t miss it.

within the remote command “set -x” cause bash to echo all commands

I’m used to how svn export works, and have used this in a number of release scripts.

Git doesn’t quite have an equivalent

The code in chapter 7 of pro Drupal development has a bug.

The $instance array that you need to pass to field_create_instance() needs to be as below.

Drupal lets you add a taxonomy term to a node and if you use the GUI you can have a nice auto-complete widget that takes term name - and iof the term doesn’t exist yet you get a new term created when you save the node.

I wanted to access the same functionality on node I am generating from external data.

This wasn’t obvious

There are various other posts on this - but mostly assuming you will put a file.

In my case I want to put the contents of a string so I needed to create a temporary filehandle.

One of those posts for myself in case I need to come back to this later

I have a new PC which is very fast apart from problems with disc access seeming slow (and the disks being physically noisy)

The following related links led me to try a solution

The music player banshee which is part of the default Ubuntu setup pops up a message each time a new track starts playing.

To turn this off

I read this post the other day and found it really inspiring - so many things to do and learn…

http://bergie.iki.fi/blog/my_secret_agenda_for_php_content_management_systems/

Links within that blog that I found especially interesting

The main svn server I’m working on has finally upgraded to svn 1.5 - so easier merging is now possible - hooray.

But we’ve been seeing merges that should only affect one file resulting in property changes on lots of files/directories. This isn’t especially harmful - but it is annoying and makes reviewing the merge harder because of the extra noise.

It turns out that this extra mergeinfo is likely because of earlier merges on subtrees http://blogs.collab.net/subversion/2009/11/where-did-that-mergeinfo-come-from/

It is possible to remove the subtree mergeinfo via this command run from the root of the branch

I wanted to write some automated tests for CSS changes and bugs, these type of issues are quite prone to regression so re-running the tests has a large benefit.

It is possible to add new assertions to selenium via the user-extensions.js file

The following adds a test for computed style, this only works in firefox as far as I know - but some automation is better than none