Date: Fri, 23 May 2008 16:15:13 -0500 From: Reid Linnemann <lreid@cs.okstate.edu> To: montag@activeattack.com Cc: freebsd-questions@freebsd.org Subject: Re: SVN Advice Message-ID: <483733E1.2030100@cs.okstate.edu> In-Reply-To: <60253.192.168.1.107.1211195138.squirrel@192.168.1.112> References: <60253.192.168.1.107.1211195138.squirrel@192.168.1.112>
next in thread | previous in thread | raw e-mail | index | archive | help
Written by montag@activeattack.com on 05/19/08 06:05>> > Hello all, > > I'm seeking to set up an SVN repository on my home machine. I've come > across the following two guides: > > http://www.bsdguides.org/guides/freebsd/misc/subversion.php > > http://www.onlamp.com/pub/a/bsd/2007/09/27/subversion-for-bsd-with-all-the-bells-and-whistles.html > > The second one is certainly overkill for what I need (I just want to use > it to manage my personal projects, since I work remotely a lot). I'd > definitely like a password protected web interface though. My issue is > the following. In both guides (and in all the other ones I've come > across) Apache is compiled with options that I did not select when I > installed Apache a while ago. I'd rather not have to redo everything I've > set up with my web server. Is there any way I get include those modules > (namely WITH_BERKELEYDB) without having to recompile? Also, any advice > relating to setting up Subversion on FreeBSD in general. > > Appreciate the help, > > montag > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" For the repo, I usually use exclusively svn+ssh protocol and DSA keys for authentication. It's a lot simpler to just let ssh do authentication than it is to futz with wrapping subversion up in apache, you don't have to mess with a separate auth database, and you get security and authorization (which users can use what repositories) as a side effect. I usually make my repo owned by group svn, change permissions so the group has write access to the db, and invite my svn users to that group. Since svn+ssh is basically local access through an ssh tunnel, there's no service to configure, and I can immediate connect remotely. For a web interface, trac's repository browser is very nice. You can front it through fastcgi on apache or lighttpd. Trac has a nice wiki link feature that lets you link in to the repository browser. For example, [123] on any wiki page will be rendered as a link to the browser that shows information for changeset 123.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?483733E1.2030100>