[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN

From: Parul <parul_at_srijan.co.in>
Date: 2005-03-01 11:22:14 CET

HI,

Since using the Apache option would mean disturbing my already running
apache configuration and also because a note in theSVN book says that
Apache option is complex, i am taking up the svnserve option.

Thanks anyways for help.

Parul Misra
Srijan Technologies.
email:parul@srijan.co.in
website:www.srijan.co.in
----- Original Message -----
From: "Graham Leggett" <minfrin@sharp.fm>
To: "Parul" <parul@srijan.co.in>
Cc: "SVN-User" <users@subversion.tigris.org>
Sent: 01-Mar-2005 3:19 PM
Subject: Re: SVN

Parul said:

> I want to set up SVN . My reuirement is a versioning system in which the
> repository can not only be accessed by different computers(majorly windows
> Platform) on an intranet, but also across the internet. Please suggest the
> most appropriate Repository set up.

I have SVN set up with the same requirements as you have. The SVN service
is hosted using the Apache svn module, which allows access both to
internet clients and intranet clients through proxies and firewalls.

The SVN webserver uses SSL to encrypt the connections, to prevent either
the code or passwords being compromised. The standard Apache
authentication setup is used for authentication.

The way I suggest you approach this is this:

- Set up a basic Apache webserver, and configure a virtualhost to host
your repository (usually svn.<something>.com). Once you get your browser
to connect to the site, you got ot the next step.

- Enable the SVN module and set up your repo as per the instructions,
probably as a test (you can setup your real repo later once you've
finished experiementing). Here you will be able to access the repo using
SVN.

- Enable SSL on the webserver, either using your own self signed
certificate , or a real certificate from Versign/Thawte/etc. Check that
SVN can access this server.

- Enable authentication on your server as per the Apache instructions.

- Last step - delete your test repo and recreate it as your "real" repo.

It's a lot of steps, but if you get each stage working in layers, it
should all start making sense pretty quickly.

Good luck!

Regards,
Graham

--
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 1 11:23:13 2005

This is an archived mail posted to the Subversion Users mailing list.