I strongly recommend against automatic deployment to your production environment on check-in. You should really have three environments: dev, test, and prod. Build code in dev and check that it all works. Then you can check in your code in dev. Deploy from dev to test and check that it works. Then deploy to prod.
How you deploy your code is up to you. We have CF Enterprise at my company and I use the Archive and Deploy features in the CF Admin for production deployments. The technology/method of deployment is secondary. The key is good process. >Kevin wrote: >Setup a project in VSS. > >Check files out to a test server, make changes there. > >Check files in. > >(Here is the part I don't know about) Make them automatically copy to >the live server > > > >How do other people setup a dev/prod environment with VSS? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:193113 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
