I am using hgwebdir.cgi on a windows machine running IIS7. I have succesfully set up the system to display all the Repos I've configured in my collections section; howerver, I would like to have granularity per repo as to which web users/mercurial users can view/push/pull from the repos. I thought that the ACL Extension might be able to do this but based on the documentation I found I wasn't confident it was the correct path. I'm looking for any documentation on accomplishing the following: Person 1 can view/push/pull from Repos A/B/C but person 2 can only view/push/pull from A/B NOT C.
|
2
|
|
|
|
|
2
|
The Mercurial Redbook goes into a fair amount of discussion on how to set up If you're using Kiln, the good news is you don't need to figure any of that out. Kiln provides very easy-to-manage access control. You can set permissions for a given user to any of none, read-only (they can clone, but not push), read/write (they can clone and push), and admin (they can clone and push, and alter permissions on the repository). Permissions can be set for both projects and repositories, with repositories, by default, inheriting the permissions of their enclosing project. To set permissions in Kiln, go to the project or repository's Settings tab. Kiln's free for students and startups, and comes with a 45-day demo no matter how big you are. You should give it a shot. |
|||||||||||
|
