What is the best way to use SVN for version control of PHP sites?
I've always just FTPed files down from sites, edited them and put them back up when creating sites, but feel it's worth learning to do things properly.
I've just commited everything to a SVN repo, and have tried sshing into the server and checking out a tagged build, as well as updating that build using switch.
All good, but it's a lot lot slower than my current process.
What's the best way to set something like this up? Most of my time is just bug fixes or small changes rather than large rewrites, so I'm frequently updating things.
Leave a Reply
- version control - What is the actual use of SVN for mergeinfo?
- What is the use of version control - SVN copy?
- svn - What is the best way to version control graphic assets on windows?
- What is the best way to version control JSON objects
- version control - The best way to save configuration files in SVN?
- More similar questions >>