On 2/15/06, Barney Boisvert <[EMAIL PROTECTED]> wrote: > > 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.
While I certainly prefer the full-fledged Apache setup for SVN (partly b/c of the far more robust authentication and management options) I have yet to see any of the problems you ran into -- I've implemented SVN for several clients with as many as 20 developers and we've accessed through svn with no lockups. You were using the filesystem backend (not BDB)? When I've seen lockups, it's always been BDB-based repositories (esp on Linux), which is somewhat deprecated. The Apache setup is harder I think for IIS shops, since there's no Apache familiarity. But it isn't rocket science. If you are an Apache shop, then by all means go straight for Apache -- you get WebDAV access for your non-techie users as well, which is a huge bonus. > 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. SVN has the built-in relocate command which handles switching repository URLs -- you *will* get into weird situations if you update some files in a working dir with file:///, some with http:// and some with svn://, but I locally use file:///, svn://, and http:// interchangably *between* projects. YMMV -- Windows servers, Windows/Mac clients. -- John Paul Ashenfelter CTO/Transitionpoint (blog) http://www.ashenfelter.com (email) [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:232725 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
