deployment

Une vidéo et un article pour revenir sur la notion de déploiement Drupal.
Cette méthode exploite l'outil d'intégration continue "Jenkins" et la possibilité d'Aegir de changer un site de plateforme (master/distribution)

• "Zero-touch Drupal deployment with Jenkins, Aegir, Git, Fabric and Drush"
• http://mig5.net/node/342

I just posted a new module called Syndeploy. It provides content changes through syndication, that can be used to deploy from staging to production. It's sort of a pull version of Deploy. Please see the project page for details. I'm just getting into heavy development now, so please reply if you have any thoughts on this. Thanks!

I was reading the site builders guide to Git (http://drupal.org/node/803746) and had a question about renaming remotes across all environments. The guide indicates to only rename the remote on your local development environment to point to your new repository.

When I update/commit/push to my new repository everything is fine, but when I pull to my development or staging environment and run git status, I get a notice that my branch is ahead of origin/xxxxxxx by 3 commits.

Should I rename the remotes in all environments to point to my repository as origin??

I am researching how we can build a rolling deploy architecture for Drupal. Here is the high level goal:

1) I begin a software deploy, users are not affected by this
2) Software deploy is complete, users are not affected by this
3) I switch my load balancer such that only certain networks are directed at the new code, my internal testers test. External normal users are not affected by this.
4) After verification, I open the site wider, allowing a small % of normal users into the site. Most normal external users are not affected by this.

At DrupalCon Chicago there was a ton of energy around Drupal's staging and deployment problem. At his keynote, Dries identified this as one of the major initiatives for the Drupal 8 cycle, and following the keynote three Core Conversations were given on the topic by myself, David Strauss, and Howard Tyson. Those talks sparked conversations which continued through the week and generated a lot of really cool ideas. This post is intended to document the ideas that were discussed (at least the ones I heard) and to use those ideas to foster further discussion.

Dear Colleague,

One of the more complex problems in managing large Drupal projects is keeping development, staging and production environments in sync. As projects grow in complexity, including multiple developers and more features, it becomes ever more important to have a reliable, repeatable process for deploying new functionality to the production website.
Join Joshua Brauer, Acquia Client Advisor, for this complimentary webinar where he'll cover:

Using version control for your Drupal project
Migrating your code, files and database between sites

Aquí les entrego la versión para Pendrive de DRUPPIX v0.12

• Se copia directamente al Pendrive.
• Ya no hay necesidad de crear CD.
• Esta la versión Drupal 7 alpha 7.
• Además de poder crear directamente el archivo persistente.
• Encriptación de los datos (Esto les puede ayudar a llevar su trabajo seguro a presentaciones).
• El Firefox tienes las extensiones Firebug, Web Devel y Tiles.
• Tiene versiones de desarrollo para módulos y theming.

Hi Techies, Drupul Geeks ... and Newspaper Content Managers--

I currently deploy my changes from dev to production using Git. I find Git a priceless tool for managing my codebase and am seeking ways to automate my deployment tasks without writing too many shell scripts involving drush etc. Does anyone use Aegir as a tool to automate git-based deployment ? Please share your experiences