Re: [Zope-Coders] SVN access using https?
Am Sonntag, den 17.07.2005, 12:42 +0200 schrieb Jens Vagelpohl: Hi guys, I noticed that right now the SVN repositories on svn.zope.org can only be accessed using the svn and svn+ssh protocols. It occurred to me that by enabling http and https and going away from svn and svn+ssh a big win can be had in terms of administration. - no need for machine accounts for developers - no need for clunky SSH key management - hook directly into existing authentication databases (LDAP of course ;) In a different situation (a Apache-based webmail setup where all underlying mail components hook into LDAP for account and configuration data) I have used mod_authz_ldap successfully to re-use existing mail system authentication data for protecting access to the webmail site. Since we already have LDAP as the basis for www.zope.org login information it should not be hard to add an attribute to contributors' records that can be used to determine access to e.g. https://svn.zope.org/svn; as a front door to the main repo or even specific sub-projects. I'm hoping to flesh that out more when I complete migrating my own repositories to SVN in the next couple weeks. Ah, and while we are at it, some nice frontend, like http://trac.edgewall.com/ would be nice. At least for browsing the repository. ___ Zope-Coders mailing list Zope-Coders@zope.org http://mail.zope.org/mailman/listinfo/zope-coders
Re: [Zope-Coders] SVN access using https?
On 17 Jul 2005, at 22:48, Stephan Richter wrote: On Sunday 17 July 2005 14:30, Tino Wildenhain wrote: Ah, and while we are at it, some nice frontend, like http://trac.edgewall.com/ would be nice. At least for browsing the repository. I like ViewCVS. It is very usable. The SVN support in ViewCVS is, pardon my french, crap. And it is extremely hard to get it working as well, it requires some horrific SWIG SVN Python binding. Tried to get it set up several times and always failed. A decent tool I have found recently is called WebSVN. It's in PHP, but seems to do a very nice job including colorized diffs, svn blame, tarball creation, etc. Basically all the things that ViewCVS does well for CVS, but doesn't do at all for SVN. It even does RSS feeds for changes (dunno what that's good for ;) See my not yet complete repository migration at http:// svn.dataflake.org for an example. The one thing it does not deal well with is resources that have been moved about with svn move - it must do something braindead there because it will complain that it cannot find the resource at the previous location. svn diff at the new location works as expected. jens ___ Zope-Coders mailing list Zope-Coders@zope.org http://mail.zope.org/mailman/listinfo/zope-coders
