Export from one instance of Cascade/ Import to another

Favorite-off Notification-off
41 Thumb-up Thumb-down
Idea by culkinj3 about 1 year ago Favorite-off - Open
Our developers work in our test instance of Cascade which publishes to our test web servers. We would like an easy way to export assets from one Cascade instance (test) so that we would import them into another Cascade instance (prod). We need 2 Cascade instances in order to OS and software upgrades etc

8 comments

  • 1 point Thumb-up Thumb-down Favorite-off by emumpton about 1 year ago Permalink
    I like this idea and would take it further.  How about the ability to package up assets or entire sites?  
    This allows for a movement between instances as well as installations and is a huge piece of a site-centric view of Cascade.
    Backup/Recovery is also complimented beyond the whole instance disaster recovery database backup now in place.  You don't have to worry about who deleted what asset and how to get it back.
  • 1 point Thumb-up Thumb-down Favorite-off by syl.turner about 1 year ago Permalink
    There is a script that lets you copy a folder from one Cascade to another using web services: http://www.hannonhill.com/new-kb/cast/folder-copy/index.html

    Since Cascade has so many crazy relationships between "Home" area assets and "Administration" area assets (such as templates => targets, blocks applied to configuration sets which use certain templates, etc.), it's a bit difficult to do at the moment.

    I believe this is something that should be definitely considered with our implementation of sites (copying an entire site?)
    • 1 point Thumb-up Thumb-down Favorite-off by mike.strauch about 1 year ago Permalink
      Web services has always been the ideal way to implement this, but I think shortcomings of the web services API make it impossible to copy everything asset-for-asset at this time.  I'm fairly certain you can do simple deep copies (meaning folders that aren't tied to too many administration assets and other home area assets) successfully using web services, but I think there are some cases where it will always fail.
  • 0 points Thumb-up Thumb-down Favorite-off by jkreuzig about 1 year ago Permalink
    In my opinion, this is one of the single most important features that I would vote for.  I think Mike is correct in that there are some cases where deep folder copies fail.  If there was a way of determining which assets needed to be copied in which order, I think the failure issues would disappear.  At least I think they would...
  • 0 points Thumb-up Thumb-down Favorite-off by wabaus 11 months ago Permalink
    Packaging up a "Site" (in v.6.x) would be awesome. Now we are always doing full clones of all sites from PROD to TEST to DEV. This would allow us to push a recent copy of the Law School to Test for training, without dumping the Business School's test of their new CSS. Also, would allow the moving of a new site up from Test to Prod, which we currently "just don't do"...
  • 0 points Thumb-up Thumb-down Favorite-off by occfs 4 months ago Permalink
    I agree. We would love the ability to "port" over portions of a site developed on a "development" cms box to our production cms box ( folders, pages, blocks, etc. )
  • 0 points Thumb-up Thumb-down Favorite-off by Nathaniel_in_MO 4 months ago Permalink
    I like this idea.  I find db "backup and restore" sufficient for moving production data to our development environment for testing, but this would be an excellent feature for moving a site/example from one instance to another that is physically separated.  Such as bringing an example site to a Cascade User's Conference for presentation.

    Also I can see a tool like this would be good for archiving complete sites.
  • 0 points Thumb-up Thumb-down Favorite-off by jbcorwin 2 months ago Permalink
    Any method of migrating things out of one Cascade Server to another would be fantastic. We currently run a dev machine alongside the live machines and being able to move items one way or the other would do wonders for my admin workflow.

No attachments


* Note - To input code samples, click the pencil icon (this will remove the WYSIWYG) then be sure to start and end code sections with @@@ (three '@' signs).  For more information on textile markup, click here.  

Sign in

Follow us on Twitter

Current Category