|
From: Jonathan D. <jd...@wu...> - 2005-03-12 22:45:18
|
On second thought, you don't need to worry about being a persnickety flibbertigibbet (phew!). SVN is smart enough to not allow you to be so foolish. My recommendation is this, if you want to work on it locally: - Get SVN installed on your local computer. - Checkout (or update) the project. Work on it. Etc. - Upload it to the server (or synchronize it) to a web-accessible location. You could choose to ignore the .svn folder when synchronizing. - Test your changes, fix your bugs, test your bug fixes, rinse repeat. - When you're done, update, then check it in from your local computer. You can update anytime on your local machine. Basically you just use the server as a test environment, but do all your work locally. --JD On Mar 12, 2005, at 1:04 AM, Jonathan Dance wrote: > An alternative is to do the development on the server. You check out a > copy on the server, set it up as necessary, make it web accessible, > and start working. You could then use Transmit + SubEthaEdit (or your > favorite FTP client/text editor) to edit the files. Alternately, you > could download the whole project and use Transmit to synchronize the > folders (this way you can browse the project locally, without being > slowed up by Transmit) as necessary. Either way, once you have tested > your changes, you can commit them on the server. Be aware: > - If you choose to synchronize, be careful when doing "svn update" - > you should synchronize your local copy UP before updating, and > synchronize DOWN after updating, else your local copy will suck and > everyone will call you a persnickety flibbertigibbet. > - Also, I highly recommend getting Transmit 3 if you're doing any work > like this; the column view is fantastic. |