Blog, backend and twitter
by michael
A few weeks ago I moved my blog over from being hosted with NearlyFreeSpeech to self-hosting on a Linode after Alex recommended them. NFS have been fantastic for the last few years but I decided I’d have a go with the flexibility that my own Ubuntu server hosted in London gives me. Bit of an experiment initially, although given the number of things I’ve put together to make it work I don’t know how easy it would be to migrate back. At first I set it up with nginx as the web server as it is nippy and light-weight, but it doesn’t support (somewhat obviously) Apache modules like mod_rewrite. Until this I hadn’t really appreciated how much stuff is written specifically with Apache as the assumed server (although as Alex pointed out, when you provide 60%+ of all web servers…) Now it’s running with nginx handling the static stuff, and Apache serving the dynamic content in a little bolted together set up. I will tweak this in the months ahead. I should say that Linode’s library has been invaluable in this process, and made much of the set up a breeze. The only thing I remotely needed to hack together was running Apache behind nginx, and that didn’t take all that long.
In the mean time I can’t recommend Linode as a server provider enough, and also hover as a domain name provider. Working with hover’s support, I got henley.co migrated from GoDaddy in under two hours. I’ll remind you that this is a process that’s meant to take 5-7 days. Absolutely can’t recommend their service and support enough on the basis of my experience so far. I’ve applied for an affiliate link so keep them in mind when you’re next looking for a domain host. Their service already beats GoDaddy hands down.
Finally I’ve added the WordPress plugin ‘Tweet Images‘ (apparently used by Stephen Fry, so I’m in good company) to try hosting my own tweeted images. Twitter and Twitterific on the iPad seem to support this API, but Tweetbot on the iPhone doesn’t annoyingly. This is all a little experimental, and with finals looming I’m probably not going to get it right in the immediate future. Apologies in advance to those that follow @michaelhenley, @mjdh, or subscribe to the blog. Hopefully I don’t balls anything up too badly!


















