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

Orchestrating Drupal + CiviCRM containers into a working site: describing the challenge

In my previous posts, I've provided my rationale for making use of Docker and the microservices model for a boutique-sized Drupal + CiviCRM hosting service. I've also described how to build and maintain images that could be used for the web server (micro) service part of such a service.

The other essential microservice for a Drupal + CiviCRM website is a database, and fortunately, that's reasonably standard. Here's a project that minimally tweaks the canonical Mariadb container by adding some small configuration bits: https://github.com/BlackflySolutions/mariadb

That leaves us now with the problem of "orchestration", i.e. how would you launch a collection of such containers that would serve a bunch of Drupal + CiviCRM sites. More interestingly, can we serve them in the real world, over time, in a way that is sustainable? i.e. handle code updates, OS updates, backups, monitoring, etc? Not to mention the various crons that need to run, and how about things like…

Building and maintaining Drupal + CiviCRM application containers

In my previous two posts, I provided some background into why I decided on using containers for a boutique Drupal + CiviCRM hosting platform, and why Docker and its micro-services approach is a good choice for building and maintaining containers.

Although I promised to talk about orchestration, that was getting ahead of the story - first I'm going to look at the challenge of keeping your application containers up-to-date with OS and application-level updates. There's a fair amount of work in that, but the tooling is mature and there is lots of good documentation.

A great place to start is to visit the official Drupal docker hub page. From there, you can pull a working Drupal code container, and it gets re-built frequently with all the OS and Drupal-code updates, so you just refresh your containers whenever you want (i.e. whenever a security release comes out, or more often to stay up-to-date).

A nice thing about that project is that it demonstrates a technique for maintaining …

The Tyee: Bricolage and Drupal Integration

The Tyee is a site I've been involved with since 2006 when I wrote the first, 4.7 version of a Drupal module to integrate Drupal content into a static site that was being generated from bricolage. About a year ago, I met with Dawn Buie and Phillip Smith and we mapped out a number of ways to improve the Drupal integration on the site, including upgrading the Drupal to version 5 from 4.7. Various parts of that grand plan have been slowly incorporated into the site, but as of next week, there'll be a big leap forward that coincides with a new design [implemented in Bricolage by David Wheeler who wrote and maintains Bricolage] as well as a new Drupal release of the Bricolage integration module.PlansApplication integration is tricky, and my first time round had quite a few issues. Here's a list of the improvements in the latest version:File space separation. Before, Drupal was installed in the apache document root, which is where bricolage was publishing it's content. This …