Skip to main content

Drupal Camp Toronto, version 2.


Looks like there will be another Drupal camp again this year in Toronto - visit the drupalcamptoronto site for details.
While I'm at it, here's a short update on a few of my projects:
  1. I finished the intranet portion of SHARE's website, which included a neat custom module that mashes up the signup module with CiviCRM and organic groups.
  2. I'm almost finished with The Tyee, an excellent alternative on-line news source in Vancouver. My work with them began with a module, still to be released, that integrates bricolage and drupal. That work went live in January and shortly after we migrated the site to a new server at Gossamer Threads who I can't recommend too highly. My latest task has been to finish off a module that allows for comment rating, it should be live by mid-April.
  3. I developed a custom Drupal module Peek which allows a drupal site user to provide sneek peeks to content on a drupal site that is otherwise protected.
  4. I mashed up gmaps and Civicrm as part of my work on the telecentre directory project. It's a little custom module (aha, also soon to be published ...) that generates google maps based on Civicrm groups.
  5. I registered the domain civicrm.ca and am using it for some small demonstration projects. I'm imagining it as a home for a group of developers in Canada that work with Civicrm, but it's a slow process....
  6. I'm looking forward to another round of development on the working overseas website that I built a few years ago.
I could go on, but I just did ...

Comments

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…