----- Original Message -----
From: "Jamie" <jam5t3r@gmail.com>
To: "Nico Kadel-Garcia" <nkadel@comcast.net>
Cc: <users@subversion.tigris.org>
Sent: Monday, April 17, 2006 8:21 PM
Subject: Re: installing server as a web host
> Thanks Nico,
>
> On 17 Apr 2006, at 16:56, Nico Kadel-Garcia wrote:
>
>> Jamie wrote:
>>> Hi,
>>>
>>> I am a web hosting provider and am looking into installing subversion
>>> on out servers for out clients to use. Are there any guides on how
>>> best to set up svn under these conditions? I am going to be using the
>>> stand alone server not the web dav version.
>>
>> *DON'T*. Seriously, use the WebDAV version. The svnserver alone is
>> distinctly insecure, since the passwords are sent in the clear. ssh
>> +svnserve works, but then you need to set up SSH services, which I don't
>> recommend for a hosted service.
>
> At the moment we can't use WebDAV, we are running cPanel which currently
> only supports apache 1.3, they are working on Apache 2 support at the
> moment but I don't know how long it will be until its released in a
> stable version.
This seems irrelevant to me: why can't you run a parallel installation of
Apache 2.x on an alternative network port?
>>> My main concerns are keeping track of users disk usage, how is this
>>> handled by subversion? Each user has their own quota so I would like
>>> their subversion repository to be within the users quota. Otherwise a
>>> user could have as much space as the server allowed, which I do not
>>> want to happen.
>>
>> Give them each their own repository. Put it in the user's "home
>> directory" on the server, and use the quotas or use the quota management
>> on *that*.
>
> I was hoping this would be the case, I wasn't sure if which ever user
> subversion runs as would be the users the files belonged to or if its the
> user that logs in.
Again, this seems irrelevant. The "subversion" user merely needs to have
write access to the repository itself, which can be in a subdirectory of the
user's home directory. If all of the subversion users have their directories
in a similar location, such as "/subversion/user1", "/subversion/user2",
etc., then all the files in "/subversion" can be set to be owned by
"subversion" and individual user quota management can be based on the
subdirectories. User's would only require protected access to their own SSH
keys if you elect to do that as part of svnserve, but setting up secure SSH
access without providing local shell access is often quite awward.
Does that make sense to you?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 18 03:28:42 2006