Installation and deployment
Version 7.x > Installation and deployment > Managing Customizations and Azure View modes: 
User avatar
Member
Member
bryanallott - 11/29/2012 9:59:23 AM
   
Managing Customizations and Azure
Is there a guide to managing customisations on a site with an Azure deploy?

Particularly, the following scenario:

I have one CMS Instance with one site that is developed locally. The site contains some content, it's own styling and some custom logic (for special instructions on the shopping cart, for example). The instance is packaged and deployed. The site is now live and is further edited regards content on the LIVE site. Users are registering on the social side- and everything is perfect! :)

In the meantime, there is more custom development going on which introduces a new payment gateway (as an example). Also, the site's style has been updated and gone through a number of iterations. Let's assume we also had to test a hotfix and applied it to the local dev instance.

What's the best way to manage publishing those changes to Azure?
Re-packaging the site doesn't seem to be an option? Or is it?
Exporting the site, and then importing it will overwrite changes (content) on the live site?

In a shared host web application (what I'm used to), it's just a case of copying across the new binaries with new stylesheets/assets and running some SQL scripts on the live database.

How do I achieve roughly the same effect using Kentico/VS/KIM tools?

If I've missed a document/article that explains all this neatly, a pointer to that would also be just great :)

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 11/30/2012 2:07:43 AM
   
RE:Managing Customizations and Azure
Hi,

I do not see any issues using the staging module. However, you need to be careful with the changes - the objects and data are being overwritten, not merged. For example you have page template v0.1 (just making up the version numbers for better imagination) with an editable text web part, this is pushed to live, editor adds some content to it. Now, you will modify the template - v0.2 and you will remove the editable text web part. Now, when you push this change to live, the web parts and its content is removed from the template too.

Best regards,
Juraj Ondrus

User avatar
Member
Member
bryanallott - 11/30/2012 2:36:01 AM
   
RE:Managing Customizations and Azure
It does need a little care in that case, yes. And also, the dev boxes tend to contain a lot of "lorem ipsum" type content when putting a new feature in and testing it; which I see is thankfully and mostly not part of synchronisation.

So hotfixes and custom code mods are managed one way (package and publish => pushes the binaries essentially)

Documents (including templates and stylesheets) are handled through staging.

Content is managed on live with it's own workflow and publishing tools inside the CMS.

Thanks!