http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660So how do you deploy to production without affecting the existing production system? http://ayende.com/3891/ideal-deployment-disaster#comment5http://ayende.com/3891/ideal-deployment-disaster#comment5Fri, 27 Feb 2009 16:38:26 GMTGreat idea. When I don't have access to the production machine, I like to make a VM Clone and setup that clone in the same network space and practice the deployment to the clone. It's not exact but it is better than a manual attempt to replicate the existing production machine. http://ayende.com/3891/ideal-deployment-disaster#comment4http://ayende.com/3891/ideal-deployment-disaster#comment4Fri, 27 Feb 2009 12:39:24 GMT"That is all beautiful and true, but f rankly not always you CAN deploy your project to production before." I think that's part of his point. He has taken care of the possibility to deploy on a production environment. http://ayende.com/3891/ideal-deployment-disaster#comment3http://ayende.com/3891/ideal-deployment-disaster#comment3Fri, 27 Feb 2009 11:58:20 GMTThat is all beautiful and true, but f rankly not always you CAN deploy your project to production before. http://ayende.com/3891/ideal-deployment-disaster#comment2http://ayende.com/3891/ideal-deployment-disaster#comment2Fri, 27 Feb 2009 08:27:10 GMTthat's why i encourage clients to have 3-4 environments: development, test, staging, and production. (not counting build machines) The idea of staging is to be a replica of production and is used for practicing deployments. Let's you shake out the loose parts, and get those deployment scripts right so the whole thing goes smoothly. late night deployments can suck, but are a whole lot better when it only takes 20 minutes and everyone hangs out at the cafe down the block until Ops says its all clear. ..then its across the street to the bar for most. http://ayende.com/3891/ideal-deployment-disaster#comment1http://ayende.com/3891/ideal-deployment-disaster#comment1Fri, 27 Feb 2009 05:04:31 GMT