About
While I (hopefully) have some skill at writing technical articles, I suck at writing non-tech stuff like "About me" Pages. But if you really want to know: I'm a German, male computer geek in my mid-twenties, interested in Application Development and Computer Games. While my programming background used to be Delphi and PHP, I switched to Microsoft's .net Platform and C# in 2007.
Apart from that, my Hobby is Freestyle Slalom Skating, and you can see a list of my gear here. Visit 4WheelFreestyle for more information. And even though I am not a big fan of social networking, I do have a YouTube Account as well.
This Blog here is meant to be a compilation of some of my thoughts and memories that I wanted to write down. Mainly for me so that I don't forget them, but maybe other people can profit from it as well. And if not, maybe you find some posts at least amusing.
Speaking of amusing: I also started to make movies, together with Kai Moosmann and Paul Mazur. The first project is The Filthy Pumpkin Show, of which we have a Trailer online now:
I read your blog over subversion and it was very helpful on getting me running... I am however running into one issue and wanted to ask for your advice. I read the second part of your suberversion blog (over multiple repos) and wanted to do something similar to what you are doing (1 auth file with multiple repos) but I am not sure how to keep someone (userx) out of a particular repo completely (I do not want them even having read access)...
i.e,
Repo1, 2 and 3 - User1, 2 and 3
Repo1 only can be accessed (read and write) by User 1,2 but 3 can read
Repo2 only can be accessed by 1 and 2 (3 can't even read)
Repo 3 can be accessed by all with full permissions..
Does any of this make sense! Do you recommend me doing anything here? I am lost and can't find anything in my searches, only similar examples like in your blog. Not a complete block in the repo for any given user...
BTW: I do like the skating - seems very cool, also checked your video on google - looks like a great time!
Respectfully,
Kevin Wilson
Hi,
thanks for the comment!
I don't have the exact Syntax handy right now, but you can work with the LimitExcept block.
Repo3 is the easiest, as the first example (the one with Require valid-user) will allow every user to do stuff.
For repo2, i _guess_ that something like
<Location /repo2>
DAV svn
SVNPath c:\repos\repo2
AuthType Basic
AuthName "Subversion Repository"
AuthUserFile c:\svn-user-file
Require user user1 user2
</Location>
should do the trick: user1 and user2 can connect and do stuff, wheras user3 cannot access this at all.
Repo1 is a bit more tricky. Again, i guess that something like
<Location /svn/repo1>
DAV svn
SVNPath c:\repos\repo1
AuthType Basic
AuthName "Subversion Repository"
AuthUserFile c:\svn-user-file
<Limit GET PROPFIND OPTIONS REPORT>
Require user user3
</Limit>
<LimitExcept GET PROPFIND OPTIONS REPORT>
Require user user1 user2
</LimitExcept>
</Location>
could work, but i have not tested it. (Maybe user1 and user2 also need to be in the Limit-block or simply put require valid-user in there)
Have a look at the documentation for Apache:
http://httpd.apache.org/docs/2.2/mod/core.html#limit
I'll try to research some stuff a bit later (kinda busy at the moment) and create a follow up post on the various Options to allow finer-granulation.