On 7/13/07, cakeFreak <[EMAIL PROTECTED]> wrote: > > Well does Capistrano works even for PHP applications?
It does. Here's a link to the best tutorial out there on using Capistrano to deploy your application: http://www.simplisticcomplexity.com/2006/8/16/automated-php-deployment-with-capistrano > about "I like to make sure my changes actually work, " > > If you branch your code via svn, you can work on the devapp, test the > changes and then merge/commit them on the trunk only when they work. > At this point you can commit the trunk to the svn repositry on the > live server. This was the strategy I was asking about. > Well what should get sincronysed is the working copy and not the > repository itself. I understand totally what you're getting at. Personally, I prefer to go with a dev to staging to production model of deployment, but that's not always possible. It's for that reason that I don't really like doing svn updates on a live server. I prefer to exports so there is no svn metadata hanging around in production directories. Just a personal preference. -- Chris Hartjes Senior Developer Cake Development Corporation My motto for 2007: "Just build it, damnit!" @TheBallpark - http://www.littlehart.net/attheballpark @TheKeyboard - http://www.littlehart.net/atthekeyboard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
