On 06/30/2010 09:48 AM, John A Parker wrote: > Thoughts? > > John
One other possibility, though less than ideal, is to use version control for your deployment. Pros: With a production snapshot of your current uPortal in a tag or branch or whatever, you can pretty easily check out the project into a directory on your production server. When you tweak a .css file, check it in, then go to your prod server(s) and do an update to pull down that change. Cons: 1) This can get you in trouble quickly with files that have to be modified for your prod server environment. Many config files will need changes for the prod environment. If you then make a new change (add a new config property, whatever) to the master copy of the config file, you can't use a simple update to pull it onto prod - you have to merge it instead. Messy, difficult to automate safely. 2) For some updates you may want tomcat to dump/reload the app from memory the way it does when you drop a new .war file into webapps. For a static web file in your skin, this is less of an issue, but for some other files you may need to kick tomcat to make it recognize the change and load the new file. Still, a version control update can be an easy way to do an incremental deployment in the right situation. You can also pretty easily test the deployment process in another directory that's safely outside of tomcat just to make sure the "svn update" won't screw anything up before you do it for real. - Aaron -- Aaron Brown ([email protected] | 785-864-0462) University of Kansas Information Services System Design Enterprise System Integration Developer
smime.p7s
Description: S/MIME Cryptographic Signature
