We encountered an issue yesterday that requires changing some Views. I don't have any heartburn about going into each region (dev, test, stage, prod) and manually changing them, but we are working to move our deployments into SVN (no choice there, please don't suggest another system). Certainly I know how to export and import, but not how that can be scripted. Does anyone do that kind of thing? If so, how? Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
Can you use features + drush? Include those views in a feature (my_views), then: * make views changes in dev * drush features-update my_views (in dev) * commit to svn * deploy to test * drush features-revert my_views (in test) * repeat as needed in stage and prod steve On Wed, Dec 1, 2010 at 9:03 AM, nan wich <nan_wich@bellsouth.net> wrote:
We encountered an issue yesterday that requires changing some Views. I don't have any heartburn about going into each region (dev, test, stage, prod) and manually changing them, but we are working to move our deployments into SVN (no choice there, please don't suggest another system). Certainly I know how to export and import, but not how that can be scripted. Does anyone do that kind of thing? If so, how?
Nancy
Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
That would definitely work, but requires a dependency on features. I guess we have to take a look at the code to see how to integrate a clean export directly into code. On Wed, Dec 1, 2010 at 11:09 AM, Steve Karsch <steve@stevekarsch.com> wrote:
Can you use features + drush? Include those views in a feature (my_views), then:
* make views changes in dev * drush features-update my_views (in dev) * commit to svn * deploy to test * drush features-revert my_views (in test) * repeat as needed in stage and prod
steve
On Wed, Dec 1, 2010 at 9:03 AM, nan wich <nan_wich@bellsouth.net> wrote:
We encountered an issue yesterday that requires changing some Views. I don't have any heartburn about going into each region (dev, test, stage, prod) and manually changing them, but we are working to move our deployments into SVN (no choice there, please don't suggest another system). Certainly I know how to export and import, but not how that can be scripted. Does anyone do that kind of thing? If so, how?
Nancy
Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
I usually just use Views Bulk Operations and cut and paste into a custom module, but I was asking the same question (postponing writing a drush handler); I just saw http://drupal.org/project/drush_views which allows to export views... Victor Kane http://awebfactory.com.ar On Wed, Dec 1, 2010 at 11:03 AM, nan wich <nan_wich@bellsouth.net> wrote:
We encountered an issue yesterday that requires changing some Views. I don't have any heartburn about going into each region (dev, test, stage, prod) and manually changing them, but we are working to move our deployments into SVN (no choice there, please don't suggest another system). Certainly I know how to export and import, but not how that can be scripted. Does anyone do that kind of thing? If so, how?
*Nancy*
Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
On 12/1/2010 6:10 AM, Victor Kane wrote:
I usually just use Views Bulk Operations and cut and paste into a custom module, but I was asking the same question (postponing writing a drush handler); I just saw http://drupal.org/project/drush_views which allows to export views...
Assuming this works well, this would be your best bet. Actually, features might be the better bet but it adds more dependencies. This is a fine second choice.
Hi Nancy, If you mean using using those exported views without having to import them, then sure: http://views-help.doc.logrus.com/help/views/api-default-views Patrick Teglia On Wed, Dec 1, 2010 at 6:03 AM, nan wich <nan_wich@bellsouth.net> wrote:
We encountered an issue yesterday that requires changing some Views. I don't have any heartburn about going into each region (dev, test, stage, prod) and manually changing them, but we are working to move our deployments into SVN (no choice there, please don't suggest another system). Certainly I know how to export and import, but not how that can be scripted. Does anyone do that kind of thing? If so, how?
*Nancy*
Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
Right, those instructions are shown when you run Views Bulk Export. I think Nancy (but I know myself) are interested in how to export views from the command line, so that the process can be automated or made part of a build script. Victor On Wed, Dec 1, 2010 at 11:11 AM, Patrick Teglia <pteglia@gmail.com> wrote:
Hi Nancy,
If you mean using using those exported views without having to import them, then sure: http://views-help.doc.logrus.com/help/views/api-default-views
Patrick Teglia
On Wed, Dec 1, 2010 at 6:03 AM, nan wich <nan_wich@bellsouth.net> wrote:
We encountered an issue yesterday that requires changing some Views. I don't have any heartburn about going into each region (dev, test, stage, prod) and manually changing them, but we are working to move our deployments into SVN (no choice there, please don't suggest another system). Certainly I know how to export and import, but not how that can be scripted. Does anyone do that kind of thing? If so, how?
*Nancy*
Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
I have no interest in using a CLI. I merely want to manually change the view on my dev site, somehow export that into SVN and then let SVN do the import on the other regions. I will be leaving this customer soon and there is no one left who knows Drupal like I do. The process must be as automated as absolutely possible. We do not have Drush or Features and I don't particularly want to install and learn them now just for this. Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr. ________________________________ From: Victor Kane <victorkane@gmail.com> To: development@drupal.org Sent: Wed, December 1, 2010 9:16:57 AM Subject: Re: [development] Pushing Views Changes Right, those instructions are shown when you run Views Bulk Export. I think Nancy (but I know myself) are interested in how to export views from the command line, so that the process can be automated or made part of a build script. Victor On Wed, Dec 1, 2010 at 11:11 AM, Patrick Teglia <pteglia@gmail.com> wrote: Hi Nancy,
If you mean using using those exported views without having to import them, then sure: http://views-help.doc.logrus.com/help/views/api-default-views
Patrick Teglia
On Wed, Dec 1, 2010 at 6:03 AM, nan wich <nan_wich@bellsouth.net> wrote:
We encountered an issue yesterday that requires changing some Views. I don't have any heartburn about going into each region (dev, test, stage, prod) and manually changing them, but we are working to move our deployments into SVN (no choice there, please don't suggest another system). Certainly I know how to export and import, but not how that can be scripted. Does anyone do that kind of thing? If so, how?
Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
On 12/1/2010 11:26 AM, nan wich wrote:
I have no interest in using a CLI. I merely want to manually change the view on my dev site, somehow export that into SVN and then let SVN do the import on the other regions. I will be leaving this customer soon and there is no one left who knows Drupal like I do. The process must be as automated as absolutely possible. We do not have Drush or Features and I don't particularly want to install and learn them now just for this.
In that case, bulk export module, select the views that need updating. Cut and paste the code, drop it into svn and check in, then deploy. You can't get more automated than this without something like features or drush.
I know you've said you aren't interested in Features, but its very simple to create a feature just containing a view, and in my experience, Views in Features seem to get rebuilt without a revert, making the process seamless at the other end. On 02/12/2010, at 6:37 AM, Earl Miles wrote:
On 12/1/2010 11:26 AM, nan wich wrote:
I have no interest in using a CLI. I merely want to manually change the view on my dev site, somehow export that into SVN and then let SVN do the import on the other regions. I will be leaving this customer soon and there is no one left who knows Drupal like I do. The process must be as automated as absolutely possible. We do not have Drush or Features and I don't particularly want to install and learn them now just for this.
In that case, bulk export module, select the views that need updating. Cut and paste the code, drop it into svn and check in, then deploy.
You can't get more automated than this without something like features or drush.
On Wed, 2010-12-01 at 06:03 -0800, nan wich wrote:
We encountered an issue yesterday that requires changing some Views. I don't have any heartburn about going into each region (dev, test, stage, prod) and manually changing them, but we are working to move our deployments into SVN (no choice there, please don't suggest another system). Certainly I know how to export and import, but not how that can be scripted. Does anyone do that kind of thing? If so, how?
If all your sites are all the same, here's the dirty thing that we do in those cases: 1) dump these tables: views_view views_display views_object_cache 2) import them into other database 3) clear cache Can't beat the speed of that. And it can be scripted easily ;)
If I was hanging around, this is the option that makes most sense. Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr. ________________________________ From: Nikola Kotur <kotnick@gmail.com> To: development@drupal.org Sent: Wed, December 1, 2010 12:16:18 PM Subject: Re: [development] Pushing Views Changes On Wed, 2010-12-01 at 06:03 -0800, nan wich wrote:
We encountered an issue yesterday that requires changing some Views. I don't have any heartburn about going into each region (dev, test, stage, prod) and manually changing them, but we are working to move our deployments into SVN (no choice there, please don't suggest another system). Certainly I know how to export and import, but not how that can be scripted. Does anyone do that kind of thing? If so, how?
If all your sites are all the same, here's the dirty thing that we do in those cases: 1) dump these tables: views_view views_display views_object_cache 2) import them into other database 3) clear cache Can't beat the speed of that. And it can be scripted easily ;)
participants (7)
-
Chris Skene -
Earl Miles -
nan wich -
Nikola Kotur -
Patrick Teglia -
Steve Karsch -
Victor Kane