what about views deployment ?
iko - November 16, 2009 - 13:48
| Project: | Deployment |
| Version: | 6.x-1.x-dev |
| Component: | views_deploy.module |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Hello,
I have been playing with deployment.module for a while (a very exciting module ! thank you), but there is no way to deploy views as there is no views_deploy.module in modules directory... May you give some informations about that ? I couldn't find any explanations. Is the module no yet ported to D6 ?
Thanks for further details !
#1
Although the deployment API could solve this. I don't think it should. The deployment API is best suited for content and basic site settings I think. I would suggest you should look into the Features module for updating views on several sites. You also need a feature server for that to work smoothly.
Read more here: http://developmentseed.org/blog/2009/sep/03/5-minute-feature-server
#2
Hmmm...
As far as I tested it, Features is somehow different, and a view imported via a Feature is dependent on the Feature (and on the features.module of course). What I find interesting with Deployment is the fact that, once a deployment plan has been pushed, the "umbilical cord" between source server and "live server" may be cut if necessary, and deployment and services.modules may be disabled if no more needed - the results of deployment plan still remaining in "live server" (unless I missed something ?). This meets my technical imperatives...
But may be I'm wrong about deployment.module.
Thanks anyway for your response...
#3
You are totally right in what you are saying. Both ways have their advantages. I haven't looked to deeply into how Deploy is managing Views deployment. But I think I'd prefer a Feature setup with a Feature Server. I actually prefer that "tight" dependency on a feature. When having it "in code" that way, it's easier to revert or update changes between sites, imho.
#4
There is actually a Views deploy module that was hung up waiting for a patch to Services which allowed you to modify an existing view. I need to check to see if that patch ever actually got committed, and if so I can commit the Views support. It is a little bit of a hack for modifying views, but it does work.
#5
@dixon_ : I perfectly understand your arguments, but in my case I do need to avoid as much long-term dependencies as possible, so features.module's behaviour is more a problem than a solution for me. Of course it may be different for anyone else.
@heyrocker : that's why I asked : couldn't understand why the views_deploy.module had been removed. Thanks for the explanation !