Date: Sun, 18 Apr 2010 09:09:09 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-questions@freebsd.org Subject: Re: version/revision control software for things mostly not source Message-ID: <4BCABE25.5080000@infracaninophile.co.uk> In-Reply-To: <20100417170814.GA5643@guilt.hydra> References: <r2ycf9b1ee01004170808w69bea524j450b018e026c3b5c@mail.gmail.com> <4BC9F1C6.8090803@infracaninophile.co.uk> <20100417170814.GA5643@guilt.hydra>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 17/04/2010 18:08:14, Chad Perrin wrote:
> On Sat, Apr 17, 2010 at 06:37:10PM +0100, Matthew Seaman wrote:
>>
>> I'd recommend subversion for this -- configure it using HTTPS and with
>> Apache's basic auth for access control. Use ViewVC for exploting your
>> repos via the web -- if you take care to set appopriate MIME types as
>> properties, then your browser should open files in the appropriate
>> applications automatically. [Verb. Sap. ViewVC looks pretty ugly in the
>> default view, but set template_dir=templates-contrib/viewsvn/templates
>> in viewvc.conf for a much better result]
>
> Actually, on FreeBSD, I think it's a lot easier to get things going just
> using the command line client -- and you can explore the local copy of
> the repository using tools on the local machine just fine. I don't think
> a bunch of extra tools like a Webserver are necessarily the best option
> for a single user. Your mileage may vary, of course.
Heh. I've spent so much time setting up apache configs that it's second
nature to me. svnserve is certainly easier to get going in a basic
setup, but tends to become rapidly more complex if you want to do
anything much beyond that. Particularly if you want to offer read-only
or anonymous access to your SVN repo -- doing that via apache is a lot
easier, and probably a lot safer.
>> Subversion is a big and complex beast, but the documentation is
>> excellent. There's a whole book you can download here:
>
> It isn't terribly complex to set up using just the command line
> interface, though, if that's an acceptable interface for the user in
> question. Once the user gets used to it, it's quite simple to use, too.
>
> If all the bells and whistles you suggested are desired, though, it does
> get to be a bit more to manage.
I find that all the effort is in the initial setup -- once it is up and
running, it's pretty sweet and simple from the user point of view.
>> For access from Windows, try TortoiseSVN.
>
> Luckily, TortoiseSVN is pretty easy to set up and use on MS Windows.
Also, if you have a Mac, you can mount a SVN repo as a WebDAV fileshare.
That's really quite nifty. The same thing should be possible from
Windows, but there are some nasty bugs which get in the way. Rumour has
it that explicitly adding a port number to the WebDAV URL makes things
happier, but I've never tried that myself.
Cheers,
Matthew
- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkvKviUACgkQ8Mjk52CukIxETQCeIa+00eIx4uYr19lSo46c5Gec
wjwAn1xqbTMNDbd4uAvfpFOspWAISjGo
=DIT3
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BCABE25.5080000>