Comments on: Finally, Drupal Gets Deployment

By: seth

seth — Tue, 21 Apr 2009 23:20:05 +0000

Unfortunately there is very little industry consensus on terminology. Words like "deploy" and "template" have different meanings in different platform communities. Bob Doyle, over at CMS Review, has been trying to put together a content management glossary but it never got off the ground. I think that we need to accept that words mean different things in different technologies and begin cross-community conversations with some level-setting and terminology definition.

By: Russ

Russ — Tue, 21 Apr 2009 22:08:54 +0000

@Adriaan Bloem

Hmm, while have come across the terms baking/frying I can still see others becoming confusing as the word “publishing” is often used within the CMS itself to reset a content-item’s state e.g. from ‘draft’ to ‘published’ (eZPublish, Plone, perhaps others).

By: Adriaan Bloem

Adriaan Bloem — Fri, 17 Apr 2009 01:58:27 +0000

@Russ, it’s customary to use “publishing” for that, not “deploying”. I.e., static or dynamic publishing (baking vs. frying).

By: Russ

Russ — Thu, 16 Apr 2009 22:35:28 +0000

Isn’t this more ‘porting’ than ‘deployment’? I have been working on a static ‘deployment’ module for the ezpublish CMS. The name came from Plone who’se ancient extension ‘CMFDeployment’ did exactly that – cooked, then deployed, a dynamic (Python) CMS-based website to a bunch of static HTML files for offline viewing, high-burst traffic sites with no real need for user-dynamic interaction (our site at geonet.org.nz is an example)

This might be a bone of contention between different CMS installations (‘deployed’ or ‘ported’)

Just thought I might mention it
Russ

By: Joe

Joe — Tue, 14 Apr 2009 15:23:34 +0000

High time! Been looking for this kind of thing in Drupal for 3-4 years. Together with the arrival of widespread unit testing and abandonment of PHP 4, Drupal 7+ should be significantly less crazy-making to manage.

Ironically, I think I’m finally enough fed up with the pains of coding custom behaviors in Drupal that I’ll be using rails/django/whatever for any future work. (I’ve said that more than a few Drupal projects ago, too…)

By: Greg Dunlap

Greg Dunlap — Mon, 13 Apr 2009 20:07:14 +0000

Thanks for the writeup. Deploy is pretty much in its infancy now, I hope to continue growing it in the coming months. I do not right now have any plans to integrate with code deployment. I feel like the tools for managing that are pretty mature (talking mostly of svn and deployment scripts like Drush) and I’m more focused on solving other problems right now. However I hope to have a patch done soon to manage file attachments. I also know there are a lot of improvements being done to Drupal’s Version Control API module, so in the future linking the two together could be pretty easy.