So, I create a subversion repository via virtualmin for a sub-server. No users can be picked to grant access to, that part of the screen is not shown. It dutifully creates the svn repository, for example, at /svn/whmcs. I try and access said repository using the username created for the main server (since sub-server has no user) and I get an apache 403 error. Password is correct of course, and it did correctly create the password file with the main servers user and password. However, no users have access.
If I add the user to the sub-servers etc/svn-access.conf file, indeed, the repository then works. Add it as follows: username = rw
So, confused as to why I cannot create one for a sub-server without having to manually edit the file? Do i have to do something weird like create a user for the sub-server (ftp user) that will never be used perhaps? before creating the repository?
Comments
Submitted by sfatula on Sun, 03/28/2010 - 23:18 Comment #1
So, indeed, I created a user for the sub-server called svn, with a simple password, then created a repository, and, indeed, it creates the right entries since I can now grant a user access.
However, it seems to use the wrong password when done in this manner. The password assigned to the new "email" user named svn is NOT what was specified when that user was created, easily verified by showing the password. So, I then had to go into apache and manager the access for the svn location and change the svn user password and then it works.
Still, seems like too much work here or a sub-server, shouldn't it just work without:
Submitted by JamieCameron on Mon, 03/29/2010 - 13:35 Comment #2
I just tested this, and it works fine for me ..
Did you first add any users on the "Edit Mail and FTP Users" page for the sub-server? Only users associated with the sub-server can be granted access to its SVN repositories - not users from the top-level virtual server.
Submitted by sfatula on Mon, 03/29/2010 - 13:39 Comment #3
It is very strange to have to create a sub-server user first. If you insist, I guess it's ok to require that though not obvious.
But, for my second test, yes, I created a sub-server user with a different password than the main server user. For the sub-server user, it did create every thing it is supposed to, but, the SVN password for the user did not work.
Submitted by JamieCameron on Mon, 03/29/2010 - 13:55 Comment #4
You don't actually have to create the user first - you could add the repository, then create the user and grant him access to the repo.
As for the login problem, are you sure you were using the full username? It will be something like steve.subserver ..
Submitted by sfatula on Mon, 03/29/2010 - 15:12 Comment #5
Of course, since change the password only made it work.
Submitted by JamieCameron on Mon, 03/29/2010 - 19:02 Comment #6
Actually, I was wrong about the username - you only need to use the first part of the username, without the domain extension.
On a test system, that works fine for me..
Submitted by sfatula on Fri, 05/27/2011 - 18:43 Comment #7