We have a repository, from which we can do an "svn up" from our development server's public_html folder via SSH. This works fine as all the latest revisions are deployed (is "deployed" the correct term?).
We have a production server, also. We can log in to this server via SSH, go to it's public_html, and do an "svn up." An exact copy of what is deployed to our development server is deployed to our production server. Here's the catch: some of the files need to be different from development to production server (primarily configuration files). How should we set this up such that when we deploy to the development server, we get the development configuration files -- and when we deploy to the production server, we get the production configuration files? New to Subversion administration and only know basic Linux. My guess is that this probably has something to do with branches. Deploy this branch to this server; deploy that branch to that server. Thanks. --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] -~----------~----~----~----~------~----~------~--~---
