We use Springloops for our hosted Subversion, and it has a very nice deploy feature. You can log in and deploy any version number of your site to a dev server or a staging server or a production server - as many servers as you actually have, you can record the deploy info there, and then deploy to it.
You can also set your Springloops account to auto-deploy after each commit. We've started doing this. We gave up on FTP, and now all our graphic designers and programmers, when they want to put something on the server, they commit it to Subversion. In his way we've ensured that what is on the server is always an exact copy of what we have in Subversion. On Feb 23, 8:21 pm, "Patrick Fong" <[email protected]> wrote: > Hi Guys, > > I'm interested to know what deployment methods everyone is using to deploy > there SF projects ? > > I'm currently using svn checkouts but I'm not very happy with that and am > looking for something a bit more advanced. I've had a quick read about > Capistrano (rails deployment) which can also be used for php and am looking > into using that possibly. Does anyone else have some suggestions or advice ? > > Cheers, > > Pat --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
