Posts

Starting at a new company is always a daunting prospect, you’re never quite sure what to expect. When I started at CTI I had no choice but to hit the ground running.

This has always bugged me, you can’t easily download Drupal to your current directory using drush. After a quick search I found this issue - https://drupal.org/node/495438 The following command works well -

During my time off I figured I’d get my dev environment setup for when I start at CTI. Using the really great puphpet.com I’ve created two new vagrant configs, the first is for Apache the second is for Nginx.

For those that don’t know me I hate HTML and CSS odd considering the profession I’m in. I love when I see people do cool presentations and I really like to know how they’ve done it.

I’ve started working on some really cool projects now that I have a bit of time spare. I have 4 that I’m running concurrently which is quite a lot considering at least 2 of them are quite big.

After 3 and a half years at Ixis I’m sad to say goodbye. I think it’s time to move on and explore new opportunities. My time at Ixis has been great, the people are amazing and it’s been a pleasure to help shape their infrastructure and deliver sites for them.

Six months is a long time, it’s a percentage of my life gone. Just over six months ago things were a lot different. I’d never have guess I’d be here right now writing this.

Just a heads up I’ll be speaking at Drupal Yorkshire on the 13th August about Drush Commands and creating your own. Which reminds me I should probably make a start on the actual content…

Here is an unedited version of the post. Raw and uncensored: After many a fruitless and frustrating discussions around git best practices here’s my bulletproof method: Tag it - if you want to release code you have to tag it.

There was an article floating around a few weeks ago about deploying large scale applications to multiple servers through bittorrent. I remember being at a talk by a Facebook developer who mentioned they did the same.