Sebastian Grewe wrote:
> If you have svn.proja.com available to serve the single repository
> proj-a the use instead of Proj-a. That way that virtualhost
> only serves one repository wihout users suspecting additional repositories.
Which implies to have separate repositories per project, yes. I t
's a better way other than having dedicated
> repositories
> per project (which is also an option).
>
> ~Neels
>
>
> >
> > Thanks,
> > Itamar O.
> >
> > -- Forwarded message --
> > From: *Itam
gt; the repository would still allow that if any got through.
>
> It's hacky ;)
> Not sure if there's a better way other than having dedicated repositories
> per project (which is also an option).
>
> ~Neels
>
>
> >
> > Thanks,
> > Itamar
tter way other than having dedicated repositories
per project (which is also an option).
~Neels
>
> Thanks,
> Itamar O.
>
> -- Forwarded message --
> From: *Itamar O* mailto:itamar...@gmail.com>>
> Date: Wed, Feb 10, 2010 at 11:00 PM
> Subject: Servi
Date: Wed, Feb 10, 2010 at 11:00 PM
Subject: Serving internal SVN path via Apache
To: d...@subversion.apache.org
Is there a way to configure Apache to serve a "scoped" repository?
e.g., if my repository root is at /var/svn/repos,
and I have top-level project-structure,
I want somethi
