>
> This might be exactly what's needed if you're, say, teaching a programming
> class where you want students to learn to use Subversion for version control
> of their projects. You don't want students to be able to mess with each
> others' code, and you probably don't want to retain their data f
On Sat, Feb 12, 2011 at 2:25 PM, David Chapman wrote:
> Repositories are meant to preserve data, implying they are relatively
> long-lived. Are you suggesting that repositories will be deleted all the
> time? If so, a master server-based configuration like httpd may not be
> appropriate for you
On 2/12/2011 1:11 PM, m irya wrote:
Yep, i could manage to get to such configuration, but here's when it
comes to the real difference with your setup: we need to manage a huge
and frequently changing user database, with each user having a small
repository.
Here's the big caveat: whenever a rep
Yep, i could manage to get to such configuration, but here's when it
comes to the real difference with your setup: we need to manage a huge
and frequently changing user database, with each user having a small
repository.
>
> Here's the big caveat: whenever a repository is added or removed (in you
On 2/12/2011 8:34 AM, m irya wrote:
The problem:
1) there's a directory on the server containing multiple svn
repositories roots, say /var/svn, with /var/svn/a, /var/svn/b, etc.
being repository roots
2) these repositories are accessed via HTTP, handled by Apache2 + mod_dav_svn
3) there's a MySQL
The problem:
1) there's a directory on the server containing multiple svn
repositories roots, say /var/svn, with /var/svn/a, /var/svn/b, etc.
being repository roots
2) these repositories are accessed via HTTP, handled by Apache2 + mod_dav_svn
3) there's a MySQL user-password database we need to use
