Originally Posted by till
1) add svnadmin to the list of jailed applications.
2) Setting up the user rights for the repository is not related to ispconfig, you should take a look at one of the the svn guides on the svn homepage.
1) done, but the client allways gets unknown command for svnadmin
. I have in chrooted applications /usr/bin/svnadmin and in app section svnadmin.
2) I thin I was not precise enough. I did not mean the access rights for the svn repository. What I mean is the following. Lets asume i have a user client1 with a domain svn.domain.tld where he wants to have his repository available.
I would configure apache like tis:
AuthName "Subversion Repository"
But the problem now is: apache has to have read & write access for the repository. But also client 1 has to have read & write access from its jailroot.
Because as far as I understand suExec works only for php execution but not for an access to dav svn. So apache does not run under the client1's user, or am I wrong?