deployment

We need a Senior developer with Drupal deployment experience to write a database deployment script. We reckon this contract will be for about 3 weeks.

Digital People Online (http://www.digitalpeopleonline.com) is a small digital agency based in Camden.

No agencies please.

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:

Overview: Transformations is an API for creating and executing data transformation pipelines, enabling higher-level modules to build stuff like Yahoo! Pipes or targeted import/export interfaces on top of it. The purpose of this project is to improve and build upon Transformations so that it not only provides a base framework but also satisfies a larger number of end-user needs, for example an AJAXified user interface.

Description:

Transformations was born out of the desire for a solution that can map any kind of structured data to any kind of other data, such as importing CSV or more complex XML files into Drupal nodes (with field mappings, obviously), exporting the data to the same files, or, if you will, providing an online converter that converts any RSS feed into Atom for example.

When performing such a large-scale transformation, some elements of the source data will likely need to be transformed on a smaller-scale level, e.g. you might need to convert a Unix timestamp into ISO date format at some point, or remove commas from a number string ("1,099.90") to conform to the target format, or perform string replacements on a given string field. At times, you might even need a combination of those transformations, or reference some other entity to construct the desired output data.

In order to do that kind of stuff, a simple mapping screen is not flexible enough, or would require lots of custom code to handle the more specific tasks. Transformations tries to solve that problem by splitting individual data transformation tasks into individual "operations" that can be chained into a larger transformation pipeline.

All this import/export malarky is actually part of a problem I identified many years ago, while writing FAPI.

FAPI in it's current state was always meant to be the first phase in a much larger project to fix a lot of the inherent design problems we have been bumping heads against now.

If the code looks 'non-drupal like' to you, keep in mind when this presentation was done, FAPI itself was new, and such sweeping changes still had an opportunity of being taken seriously. Unfortunately I suffered from burnout shortly afterwards, and extracted myself from doing serious core development.

FAPI3 - AKA Data API presentation

Read below for some comments on this :

Based on the discussions we had at DrupalCon, I've written up the beginnings of an API with a standardized set of hooks and some functions.

The details of how, for instance, the block module would save an object to disc might start through using the not-so-desirable form API, due to lack of another option. In the future, however, this could be changed using a more optimal method.

Also included is a generalized function to fetch set of default objects that are embedded in PHP (like views module or context module implement).

Discussion is encouraged. :-)

io.module

A number of solutions are springing up for deploying site configuration (spaces, patterns, etc). And solutions are starting to spring up around deployment of custom sites as well - the Aegir project and the Domains module both provide tools for pushing out multiple sites on a single infrastructure.