Basic usage of Deploy

For this demo we will create and deploy a new node, then deploy an update to the node.

So on your staging server go to node/add/story and create a new story. Give it whatever options you like and save it.
Go to admin/content/node. Check the node you just created, choose 'Deploy' from Update Options, and click the Update button.
Choose 'Live Server' from the Server select list, and enter the username and password for the user you wish your deployment to run as on the destination server. Click the Submit button.
Your deployment should go through two phases - Processing deployment plan dependencies and Pushing deployment plans.
You should end up at Deployment Log Details, which lists the node you just deployed and a Result of 'Success'.
Go to admin/content/node on your destination server. Your node should be listed there, and if you edit the node your settings should have all been transferred properly.
Now if you like you can return to this node on your source server, make some changes to the node, and go through the same process to deploy it to the destination server. Your changes should be transferred properly.

Deployment plans

You can build a deployment plan which groups together selected pieces of content to be pushed to live at the same time.

First, create an empty deployment plan at Administer > Site building > Deployment (admin/build/deploy) under the Plans tab. Click the Add a New Deployment Plan link and fill in a name for the plan.
Go to Administer > Content management > Content (admin/content/node) and select the items you wish to group together in the plan by checking the boxes.
Select "Add to deployment plan" from the Update options dropdown list and hit the Update button.
You are presented with a list of deployment plans you have created. Select the plan to add the items to and hit Submit.

Once you have set up the plan, you can return to Administer > Site building > Deployment (admin/build/deploy) and use the "push" link for a plan to push it live. You will be prompted for the destination server username and password and the process will follow as outlined above.

Comments

deploy twice and your production content updates first, not 2nd

mooreds commented 23 August 2009 at 03:27

If you deploy nodes twice and your stage content changes both times, but your production content only changes the first time, check your server time. The deploy module has a check to see if the node on production has changed more recently than the node on stage, and doesn't push the content. If this is the case, you won't see a 'proceeding' message, but neither will you get an error message.

nodes don't deploy

mooreds commented 23 August 2009 at 03:28

Make sure you have file upload turned off. See this issue: http://drupal.org/node/461062

This is the tracking issue

robertDouglass commented 13 January 2010 at 00:19

#459192: Deploy module doesn't work with upload module

username and password fields doesn't appear, ajaxSubmit issue ?

mattew commented 13 October 2010 at 09:52

Hi,

I set up a new deploy environment for a website this morning. For information, i have updated all my modules, including Drupal.

When selecting the server to deploy to, after choose "Deploy" for a node, fields for username and password doesn't appear, like they used to.

Firebug report a problem with ajaxSubmit :
$(element_settings.element).parents("form").ajaxSubmit is not a function
http://localhost.askia/misc/ahah.js?a
Line 99

What a pity, this module is so great !

Best regards,

Resolved

mattew commented 14 October 2010 at 17:29

I have found the problem.

It was a conflict with my newest version of jQuery loaded with the theme, it appears that ajaxSubmit of jquery.form plugin was down for this specific usage.
I'm using some of latest jQuery features for my website (like mouseleave for example), so i can't rely on the old jQ version given by Drupal.

I had to load manually the newest jQ version before all other javascript in the section and put a jQuery noConflict variable between my newest version load and the oldest one from Drupal. So now i have to use my noConflict variable to use latest jQuery features. I hope it won't be a problem for the future, especially for plugins.

Best regards,

P.S : this article help me to apply the noConflict trick : http://web.enavu.com/daily-tip/using-multiple-versions-of-jquery-on-the-...

Doesnt update an existing node

vj1200 commented 2 March 2011 at 20:09

I followed the steps Basic usage of Deploy, i could transfer a node successfully, but could not update the existing node.
When i update the existing node on the staging server and follow the same process to deploy, the node is transferred as a new node in the production server and the older one remains as it is