Skip to main content

Circling Around Again

I've just finished "Three Day Road" by Joseph Boyden, an appropriate novel for this time of year when death is in the air, in a "circle of life" kind of way.

It's also just over 5 years since I started out working on my own, and a year since I started working again with a couple of old friends. One of those (Reema) has just found herself a real job so she'll be leaving us and I wish her well. Starting new things is usually harder and slower than I imagine, which is good, since I'd probably not bother otherwise.

At the machine level: we've just brought online a new server and moved all the services left on my oldest server in preparation to shut it down. Shutting down old servers is rarely worth it from a time/finances point of view, but it seemed like the right thing to do in this case, in spite of the backlog in client work I've now accumulated.

And of course, in the global scheme of things, death has the excellent function of making space for new things, and that's very true in this case. My new server is using pressflow and varnish to be super scalable for a couple of new big sites, one of which is already humming along on it (http://socialinnovation.ca). Rob Ellis has also installed apache solr on it, and it's a huge relief to be able to use it on my larger sites: compared to stock Drupal search, it gives better results, it's faster, and the site database backups are about half the size (having the search database being backed up always seemed ridiculous anyway).

Popular posts from this blog

Varnish saves the day, in unexpectedly awesome ways.

Four and half years ago, I wrote a blog post about Varnish, a 'front-end proxy' for webservers. My best description of it then was as a protective bubble, analogous to how it's namesake is used to protect furniture. I've been using it happily ever since.

But last week, I got to really put Varnish through a test when the picture here, posted by Fair Vote Canada (one of my clients), went viral on Facebook. And Varnish saved the server and the client in ways I didn't even expect.

1. Throughput

Varnish prides itself on efficiently delivering http requests. As the picture went viral, the number of requests was up to about 1000 per minute, which Varnish had no trouble delivering - the load was still below 1, and I saw only a small increase in memory and disk usage. Of course, delivering a single file is exactly what Varnish does best.

2. Emergency!

Unfortunately, Varnish was not able to solve a more fundamental limitation, which was the 100Mb/s network connection. Becaus…

What to do in the age of Trump?

Well, that's the question of the day. If you're part of an organization that does advocacy work, rather than waiting to see what happens first, might as well get yourself ready, even if the details are sketchy still. Here's one opportunity that's ready for you now, message courtesy of Steve Anderson of OpenMedia.

OpenMedia, David Suzuki Foundation, SumOfUs and a range of other organizations are supporting a new shared set of civic engagement tools.

Vancity Community Foundation is providing some support to subsidize some of the cost of the tools to select values-aligned organizations that sign up before February 28th.

Interested? You can learn more or book a demo from here: http://tools.newmode.net/

Here's some live examples of the tools you can take a look at:

1. Click to Call: http://www.davidsuzuki.org/blogs/healthy-oceans-blog/2016/11/to-help-protect-canadas-oceans-weve-made-it-easy-to-call-your-mp/#newmode-embed-4-266

Check out this video of David Suzuki's d…

Me and varnish win against a DDOS attack.

This past month one of my servers experienced her first DDOS - a distributed denial of service attack. A denial of service attack (or DOS) just means an attempt to shut down an internet-based service by overwhelming it with requests. A simple DOS attack is usually relatively easy to deal with using the standard linux firewall called iptables.  The way iptables works is by filtering the traffic based on the incoming request source (i.e., the IP of the attacking machine). The attacking machine's IP can be added into your custom ip tables 'blacklist' to block all traffic from it, and it's quite scalable so the only thing that can be overwhelmed is your actual internet connection, which is hard to do.

The reason a distributed DOS is harder is because the attack is distributed from multiple machines. I first noticed an increase in my traffic about a day after it had started - it wasn't slowing down my machine, but it did show up as a spike in traffic. I quickly saw that…