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

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…

Upgrading to Drupal 8 with Varnish, Time to Upgrade your Mental Model as well

I've been using Varnish with my Drupal sites for quite a long while (as a replacement to the Drupal anonymous page cache). I've just started using Drupal 8 and naturally want to use Varnish for those sites as well. If you've been using Varnish with Drupal in the past, you've already wrapped your head around the complexities of front-end anonymous page caching, presumably, and you know that the varnish module was responsible for translating/passing the Drupal page cache-clear requests to Varnish - explicitly from the performance page, but also as a side effect of editing nodes, etc.

But if you've been paying attention to Drupal 8, you'll know that it's much smarter about cache clearing. Rather than relying on explicit calls to clear specific or all cached pages, it uses 'cache tags' which require another layer of abstraction in your brain to understand.

Specifically, the previous mechanism in Drupal 7 and earlier was by design 'conservative' …

Confused by online payment processing? You're not alone.

In the old days during "polite" conversation, it was considered rude to talk about sex, politics, religion and money. You might think we're done with taboos, we're not (and I'll leave Steven Pinker to make the general argument about that, as he does so well in The Better Angels of Our Nature).

The taboo I'm wrestling with is about money - not how much you make, but about online payment processing, how it works, and what it costs. In this case, I think the taboo exists mainly because of the stakes at hand (i.e. lots of money) and the fact that most of those who are involved don't get much out of explaining how it really works - i.e. the more nuanced communications are overwhelmed by sales-driven messaging, and the nuanced stuff is either proprietary secrets or likely to get slapped down by the sales department.

In other words, if you want to really understand about online payment processing because you want to decide between one system and another, you'…