Posted by matt2000 on December 31, 2009 at 11:15pm
10 followers
Jump to:
| Project: | Content Distribution |
| Version: | 6.x-1.2 |
| Component: | Documentation |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Could you comment on the differences between this module and Deploy module (apart from the obvious fact that deploy also supports configuration deployment.) When is Content Distribution a better choice that the content deployment capability of Deploy?
Comments
#1
#2
And also http://drupal.org/project/clients
#3
Subscribing... I'm curious about this, too.
#4
Having looked at all three modules, I would say:
- Deploy is geared towards having a staging site. You create a plan on your staging site, and when you are ready to deploy it, you push it out. There is no automation yet, and each time you push only to one receiving site. From what I can tell, the idea is that you have a private staging site with the nodes you need to start new sites. When you have a new site ready, you push out content to it one time.
- Clients works with Feeds module. This means that for my own purposes it has a big limitation in that it only retrieves nodes of one type at a time. I do however like its approach to abstracting the idea of a client -- it may be Content Distribution ends up as a plugin to that.
- Content Distribution is geared towards a single hub site with content that you frequently want to add or update on one more receiving sites. The idea is that you have lots of sites that need the same content -- eg suppose we had several concurrent Drupal conferences and wanted to sync news stories and sponsors across them. This would allow you to have a single site where the content lives, and multiple retrieving sites that update from it.
They are all rather similar, and yet sadly none of them is yet flexible enough to cover use cases from the other ones :/
#5
Having said that, we really need to start thinking about bringing these projects closer together -- I've just been reminded that we're more or less going to be duplicating work already done by Deploy if we add a feature here to distribute node comments :(
#6
By the way, you forgot to mention YAMM - http://drupal.org/project/yamm. I have not tested it, but it seems to be similar to Deploy.
You are right that these modules are very similar in the solution they offer. But because these modules achieve that solution in different ways, the user has to choose one of them. And that means that all of these modules will have similar functions somewhere.
For the future:
Perhaps it would be interesting to create a base module with functions that are used by all of these modules. Or to merge them all to a big distribution / deployment module...
#7
Personally, I think deploy & clients have the right idea by building upon Services module (literally for Deploy, conceptually for Clients). I'd like to see progress in that direction.
#8
Another one (well, two) seems to be Publish/Subscribe:
http://drupal.org/project/publish
http://drupal.org/project/subscribe
See issue #821392: Duplication with Content Distribution
#9
Subscribing.
#10
Subscribing.
#11
subscribing.
#12
Oh hello. You should probably go and read #1083038: migrate to content push?
Content push does what this module did, but on top of a common framework module for moving Drupal content around called Transport.
#13
Automatically closed -- issue fixed for 2 weeks with no activity.