> I would also recommend > getting svnserve running and use the SVN:// protocol.
I'd recommend against this. If you can set up Apache 2 and run Subversion through the included WebDAV module, that'll give you a far more robust and scalable solution. In particular, it will avoid locked repositories that result from concurrent access - something that svnserve (and file:/// access) can't protect against. If you've only got one developer, probably not a huge deal, but if you've got two or more (or forsee it in the future), I'd recommend the Apache route from the start. I started with svn:// connections as a single user, and I was able to lock up my repository on probably a weekly basis. Hasn't happened once since setting it up through Apache a month or so later, even with concurrent access. At the very least, NEVER mix access modes. Do everything through the same mechanism, whichever you choose. Apache does some internal magic to speed certain operations, and it plays eggbeater with your repository if you then connect with a file:/// or svn:// connection. This applies repository wide, so if you have three projects in a single repository, make sure they're ALL accessed via the same protocol. That means updating EVERY working directory if you change protocols in the future, which is a very strong argument for picking the right one from the get go. Note also that you can happily run Apache on a non-standard port (81 or 8080 or whatever) if you also need to be running Apache 1.3 or IIS on port 80. cheers, barneyb On 2/14/06, Pete Ruckelshaus <[EMAIL PROTECTED]> wrote: > I've been using SVN (Subversion) for the past 6 months, after having > used Perforce and then CVS before that. > > CVS had its issues and annoyances, but I wasn't the guy who was > responsible for it, so no biggie. Perforce was OK, I was the only > developer so I was able to get by with the free licensing, but it also > had its idiosyncracies. So, I switched to SVN and have been quite > happy. I have a Windows 2000 Server file/dev server at home that is > my SVN repository, and updates, commits, etc. are all quite easy, > especially if you're using Tortoise. I don't really branch that much, > mainly because I don't feel the need to since I'm the only developer > and I use SVN as insurance against my own stupidity. > > Now, when it comes to IDE integration, Homesite/CF Studio have it, in > a sense. In the directory view (upper portion of the right hand > pane), you can right click on a directory and have access to the SVN > commands (add, commit, revert, update, etc.) if you're using > TortoiseSVN (which I highly recommend), but it's of course at the > directory level. However, with SVN, you don't need to be checking > files in and out, so it's not a big deal. Technically, though, you > also have SVN functionality at the file level, you just need to go > into the file properties and click the Subversion tab and it's pretty > much all there in the log area. > > The hardest part of setting up SVN was getting used to the terminology > and figuring out how to do basic things like creating new repositories > and checking them out to your dev machine. I would also recommend > getting svnserve running and use the SVN:// protocol. > > I hate to boil it down to this, but if I can get it up and running, > anyone can. What's more, it's free and well documented, so there's > little to lose. > > Pete -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:232312 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
