deployment

At IDEIA we are currently working on a new (simple) staging solution.
I have evaluated many systems like : Features, Drush, StrongArm, Context, Patterns, DBScript, Migraine, Deploy, Node_Import, Feeds, Staging, etc...
The common problem encountered with theses modules are :
* they are compatible with few modules
* needs many manual operations and double checking
* handle only content, or config but not both of them

The only "global" solution is DBscript, but it's not a real module, not easy to configure (you must describe all foreign keys of your DB in a config file).

So we came to a new method, based on MySQL auto_increment_offset. These ID pattern allow to know from which DB came any content of any table in the DB.
For example, if we choose that ID terminated by 1 are "prod server", ID terminated by 2 are "test server", and ID terminated y 3 are "dev server".
So merging dev / test / prod is rather simple with some basic SQL UPDATE and DELETE for each table.

hi,

i've just created a Settings Audit Log module.

http://drupal.org/project/settings_audit_log

it uses a trigger on variable to log all changes by user.

looking for reviews, feedback, and ideas for modules to build on top of this using the audit data.

cheers
justin

Kicking off a discussion here surrounding the whole area of content deployment à la Deploy module. I'm starting work on a comprehensive deployment system for a large client and we'll be contributing back our code. I want to try to minimise duplication of efforts by staying in touch with others who are already working on extensions or enhancements to Deploy and related module, so that I can build on existing code and not re-invent the wheel. Heyrocker has told me that he's done a nodequeue deploy module, for example, which is one of the main things we'll need.

Dear all,

I thought it would be very helpful if I would bring it up here.

Our situation is that we are moving a large, multi-user knowledge management Portal into private beta. While we wish to have a "live" version of the site, with content creation, file upload , image upload and addition etc, we wish to maintain active development on several aspects of functionality.

As we all know, one of Drupal's major shortcomings is exporting configuration. I believe that the source of this problem is that there is no standard way to store and retrieve settings. Most modules use variable_get and variable_set. The problem with this is that there is no association between a variable and a module.

I propose an api for saving and retrieving settings. I am currently working on a settings module as a proof of concept.

Here is a glimpse of the current api:

Fiz todas as mudanças, fiz o commit para o controle de versão, e agora?

http://www.slideshare.net/eaton/drupal-deployment-presentation

Apresentação muito boa sobre como proceder para colocar em produção seus sistemas/sites em Drupal, sem medo de problemas de integração.

For anyone who attended the Florida May meeting where I presented a case study on my work for ScubaDiving.com, which focused a lot on installation profiles.. well I finally posted some details on my blog on how I built it, along with some related details:

http://www.mc-kenna.com/drupal/2009/06/building-drupal-installation-prof...

Please post comments on my blog if you have any feedback, in the interests of keeping the discussion centralized.

We're proud to announce the first release candidate of the 0.2 release of the Aegir hosting system for Drupal.

Ægir is a set of contributed modules for Drupal that aims to solve the problem of managing a large number of Drupal sites. It does this by providing you with a simple Drupal based hosting front end for your entire network of sites. To deploy a new site you simply have to create a new Site node. To backup or upgrade sites, you simply manage your site nodes as you would any other node.

This release is the first release candidate of our 0.2 development cycle, which has been focused on complete support for running multiple concurrent Drupal releases, and managing upgrades of sites between Drupal releases. This release has been focussed on improving some our experimental multi-client functionality, as well as fixing bugs for our final release.

Aegir is in code freeze, and only bug fixes and usability improvements will be allowed in. The final release of Aegir will occur shortly after the 2.0 final release of Drush, and we will only be making changes to Aegir to maintain compatibility with Drush upstream.

we have a LIVE website, with active (recurring) paid subscribers...
every month - they get charged on their credit card through paypal.

(so far - all good)

now - while creating the next version, updates, etc -
on DEV - we migrated all live user info and started working with it
(ouch)
and then - all our paid subscribers - got a false message - that their credit card cannot be charged!

my question is -
moving forward, as we are going to have automatic notification on content added, newsletters, recurring payment, etc.

is there any safe method / workflow -

Hello,
So here is my problem, I created a multi-site installation of Drupal using a single source tree with 50+ sub-sites using symlinks for each. The problem I have is if I try to create a page alias on a sub-site that is the same as another symlink sub-site directory Drupal will not display the page. Instead Drupal will validate the URL as the first sub-site's home page.
Here is an example

1) I have a default site at:
www.example.com

2) I have two sub-sites
www.example.com/math
www.example.com/arts

If on the math sub-site I attempt to create a page using pathauto like so: