The pros and cons of running a distributed team.
Over a series of blog posts we’d like to explain how we go about running a distributed company, why we chose this model, what we found works, what didn’t, and how it is really possible to be a global business of home workers.
Those with a sweet tooth found the Code Enigma booth at this year's DrupalCamp NW an excellent source of nutrition. Find out more about what was a truly excellent event.
Code Enigma was proud to be a Gold Sponsor of
An actual performance test, like-for-like, of Panels versus Block
Panels has been around for a long time now. It gets mixed reviews. It's a bit like the Marmite of Drupal - you either love it or you hate it. Personally, I'm a fan, for a number of reasons that warrant blog posts of their own.
We make a fascinating discovery about our France-based Director and Bletchley Park links
In something of a bizarre and fascinating twist of fate, it so happens that I live next to (and used to live in) the little French town of Uzès, in the middle of the French garrigues, surrounded by wild hills, even wilder pigs and grape vines.
Code Enigma recently funded a sprint to help get the Views module in to core for Drupal 8. This is the 'how' and the 'why'. One of our developers, Alasdair, will be following up with the 'what'.
Code Enigma are sponsoring a Views In Core sprint in Paris, France, from 26th - 28th August 2012.
Following on from Earl Miles’ request that people help fund the Views In Core initiative for Drupal 8, Code Enigma is proud to announce a Views In Core sprint, in Paris, straight after DrupalC
Firstly, Happy New Year to all our friends on the Gregorian calendar like us. We're guessing that's most of you, but perhaps not all.
Contrib Hour time again! (Well, actually it was yesterday, but we have a bit of a mad rush up to Christmas, so I'll keep it brief.) Alasdair
Our use case here is if you have a lot of data you want to insert in the MySQL - data that you might usually use the Drupal UI for, but there's so much of it you'd rather not if you can help it!
The roundup of what the Code Enigma team did in their weekly hour of maintaining their contributed Drupal modules.
That time again! Apologies for the dry title, but since this is a weekly event, doesn't seem much point in trying to dream up a snappy headline week in, week out. I guess I'll never be a columnist! So, without further ado, here's what the team did today:
We pride ourselves here at Code Enigma in doing lots of work for the community.
Supporting information for the talk we gave at Drupalcamp Toulouse
A big thank you to everyone who joined the DrupalCamp Toulouse English track for my opening session, and I hope it was useful. Also, special thanks to Miguel Jacq for his input, both to the talk and to our systems in general.
A look behind the scenes at our specially developed hosting system.
We'd been talking since we started trading (almost exactly a year ago, as it happens) about setting up something that would smooth our deployment process and allow us to offer solid, professional hosting to our clients.
I was looking for a Skype recorder that works in Linux and I came across this application:http://atdot.ch/scr
Just because we've chosen to specialise in the Drupal CMS as our main tool - that doesn't mean we recommend hitting every nail with it.
I'd like to start by quoting Jeff Goldblum's character from the 1993 blockbuster Jurassic Park, Dr. Ian Malcolm, when he says to Richard Attenborough's park owner character, John Hammond:
This is now my first Drupal 6 to Drupal 7 upgrade. Not without hitches, but all in all not too painful. Hope you like the new look.
Step by step guide on how I went about updating Fedora 12 to 13
Fedora 12 "end of life" just came around, so I decided to update to Fedora 13 while things were quiet over Christmas. Fedora ships with a preupgrade app which manages the update process, so in theory this should do it: su -c "preupgrade"
Wow, long lapse in posts there. Sorry folks. On with the show: Here's the problem. The Drupal security team do a fine job, following up on reports, auditing contributed modules with a point release to check for security weaknesses, working on core. It's all good, except for one thing:
Tutorial for Setting Up Git and Gitosis On CentOS 5.2
This article is a tweaked version of several tutorials around. Many of the original links courtesy of Adrian Simmons.
Before we get started I'm posting this code for reference but, had it occurred to me, I would have worked on adub's Clients module instead of starting totally from scratch.