Re: Architecture question

Use a separate server, or very carefully configure the Apache installation to allow access to only certain projects, or many other approaches are possible.

Me, I'd tend to put the alternate server on an alternate IP address and carefully control access to *that* as a virtual server in the Apache configuration. That allows you to set the firewall rules to access only that location, but it leaves you vulnerable to mis-configurations of the Apache server and unauthorized user access to other repositories or parts of the repository. If possible, why not simply use a separate machine for the SVN server/Apache server that will allow some public access.
  ----- Original Message -----
  From: Ing. Francesco Dalan
  To: users@subversion.tigris.org
  Sent: Thursday, March 16, 2006 9:19 AM
  Subject: Architecture question

  Hi to all,
      I'm new to SVN. It is possible to maintain the SVN server and the http server separate? I'd like to put the svn server behind a firwall and use the external http server (Apache 2.0) to publish (in read only) some projects. How can do it?

  Thanks in advance

  --------------------------------------------------------------------------------------
  Ing. Francesco Dalan
  M.B.M. Italia S.r.l. Via Pellizzo 14/A 35128 Padova
  Tel. +39.49.8995731 Fax +39.49.8995722 Cell. +39.348.3675906
  E-mail : f.dalan@mbm.it
Received on Sun Mar 19 17:19:15 2006