The following software upgrade strategies provide general guidelines and principles. Please use discretion at all times to develop your own software upgrade strategies that are sufficient for your application and environment.
If you are only making minor updates to your site and there is no risk of possibly breaking your application, it's probably safe to make these "rolling upgrade" changes on the live running servers. For example, you may need to perform a simple code push of some minor bug fix patches to the current release or perhaps you have a slightly modified CSS file that you want to apply across your site. As long as you know those changes will not break your site, you can run a single operational RightScript to make these changes on the live production servers.
For example, let's say you just had a major software release last week and now you need to push out some minor bug fixes. You need to update your application servers so that they use the latest branch in your SVN repository.
Note: This tutorial assumes that you've followed best practices and defined the SVN_APP_REPOSITORY input at the Deployment level and not at the individual Server levels. See Inheritance of Inputs.
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.