Category → drupal
Packaging Drupal Modules or not ?
So John wrote down his experiences on deploying Drupal sites with Puppet .
It's not a secret that I've been thinking about similar stuff and how I could get to the best possible setup.
John starts of with using Puppet to download Drush... while I want to use rpm for that ...
I want my core infrastructure to be fully packaged... not downloaded and untarred. I want to be able to reproduce my platform in a couple of months , with the exact same versions I`m using now .. not with the version that happens to be on ftp.drupal.org at that point in time, or with ftp.drupal.org being down.
Now the next question off course is what's the core infrastructure.
Where does the infrastructure end and does the application start. There's little discussion about having a puppet created vhost , an apache conf.d file, a matching .htaccess file if wanted , and the appropriate settings.php for a multisite drupal config.
There's also little doubt to me on using drush to run the updates, manage the drupal site etc . Reading John's article made me think some further about what and when I want things packaged.
John's post lead to a discussion on #infra-talk on getting all drupal modules packaged for Centos with Karan and some others
In a development environment I probably want to have periodic drush updates getting the latest modules from the interwebs and potentially breaking my devs code. But making sure that when you put a site in production it will be on a fairly up to date platform, and not on the platform you started developing on 24 months ago.
In a production environment however you only want tested updates of your modules as indeed they will break code.
It's probably going to be a mix and match setup having a local rpm/deb repo with packaged modules that have been tested and validated in your setup and using drush to enable or configure them for that production setup.
But also having a CI environment wher Drush will get the new modules from the interwebs when needed. and package them for you.
To me that sounds beter than getting all the available Drupal modules and packaging them, even automated, and preparing a repository of those modules of which only a small percentage will actually be used by people.
But I need to think about it some more :)
Technorati Tags: 
Trackback URL for this post:
Fosdem 2010
Fosdem 2010 was my 10th fosdem Edition (including the first OSDEM)
As every year Fosdem suffered even more from it's own success.
On Friday evening ther was the obligatory Beer event... however as people need to eat to .. the Devops crowd fled the scene
I had made reservations for a 20 something group and with the CentOS crowd joining us (as there was some overlap anyhow) we were 25 when we arrived in the restaurant .
Dinner and Discussions were great .. I learned about some new projects and we had some insightfull dicussions on how fat your thin foil should be ...
After dinner we went back to the Beer Event were lots of Free Beer was tasted ...
Saturday was the first full day of Fosdem, as usual Fosdem was the victim of it's own success , too much interresting stuff to see .. too little time.
Lots of Devrooms had the "FULL" sign put up more than you want as a visitor ...
I never even made it into the Drupal or NoSQL rooms :(
Sadly I had to correct Ploum's first law but for a lot of people .. Fosdem each time means the battle choosing which presentation you'll go to ... If you can even make it to the talk .. as usually the the hallway track is much more interresting :)
The MySQL devroom was on sunday but on saturday the crowd met in an Italian place nearby the Fosdem campus to get to know each other and chat a lot ..
The discussions ranged from French vs Canadaian and the future of Forks
During Saturday afternoon @patrickdebois suggested a Devops Meetup for Breakfast ... and some how that also happened ...
When I arrived at Fosdem on sunday morning they were still there :)
I spent the biggest part of Sunday in and around the MySQL devroom listening to a bunch of interresting talks
My own talk went fairly well given the time constraint .. sqeezing content for an hour in 20 minutes means you can't really go deep into the topics ...
My initial plan was to only focus on Pacemaker integration however the community had voted for the overview talk :)
After my own talk it was almost time to head to the Janson auditorium for the Footnote of Greg Kroah-Hartman, and as on any Fosdem .. there once again had to be Beer
