deployment

Brico dépôt is a well known chain of DIY stores in France.

Among their requirements were:

• Handle all of the over 100 depots.
• Import of the product data from SAP every 24 hours
• Content update every 24 hours
• about 1200 catalog pages + other categories to handle
• about 20.000 products and articles in each store. Possibility of variation in prices and availability.
• DIY layout for website managers.

Topics will be

• Import data from 3rd party application.

This session will illustrate the use of the Aegir hosting system to simplify the life of developers and administrators, by automating a lot of the common tasks involved in deploying sites.

In this panel, we will be discussing the challenges of team and site management in an enterprise Drupal environment; as well as the solutions we have each found to overcome these issues. The topics covered will be:

* Subversion management of a large Drupal installation, with multiple branches and tags for development and deployment.
* Testing newly developed modules and patches for deployment
* Managing a large distributed team of developers
* Managing Drupal upgrades and specifically an upgrade to Drupal 6.X

We know all the "drill" of migrating a site:

• Put your site on maintenance.
• Backup your database and code
• Disable all your modules (do this with 50+ modules)
• Update your core and modules code
• run update.php
• check for errors in update screen
• activate a module
• run update.php
• check for errors in update screen
• repeat last 3 actions until you have migrated all modules

And then we are not talking about migrating buddylist to friendlist or views 1.x to views 2.x.

Note: the description of this session needs to be updated.

How reliable is your web site? If one server at your hosting provider goes down, will it take your site with it? How quickly and confidently can you restore from backups? You DO have backups, right?