We've been using trac and svn internally with fairly good results. Now we'd like to open up parts of our system to external vendors - eg. we'd like to create an area on the twiki for our external designer to upload images, document things, and so forth. We need to be able to restrict his access to only that part of the twiki.
我们一直在内部使用trac和svn,效果相当不错。现在我们想向外部供应商开放我们系统的一部分 - 例如。我们想在twiki上创建一个区域,供我们的外部设计师上传图像,记录事物等等。我们需要能够限制他只访问twiki的那一部分。
Similarly we have external developers working on specific modules that we'd like to provide twiki and svn access to, but only for their subset of the project.
类似地,我们有外部开发人员在处理我们想要提供twiki和svn访问权限的特定模块,但仅限于他们的项目子集。
We started to do this with trac, then switched to pursuing basecamp, then basecamp alternatives, and then generally floundered.
我们开始用trac做这个,然后转向追求basecamp,然后是basecamp替代品,然后通常会陷入困境。
What do you recommend?
您有什么推荐的吗?
1 个解决方案
#1
1
We implemented this approach:
我们实施了这种方法:
For Trac you could try Fine Grained Permissions to control access to the wiki pages. Rest of privileges can be managed somehow with standard permissions.
对于Trac,您可以尝试使用细粒度权限来控制对Wiki页面的访问。可以使用标准权限以某种方式管理其余权限。
For the SVN access, you can use the authorization method provided by your server.
对于SVN访问,您可以使用服务器提供的授权方法。
We also have LDAP as authentication mechanism for both Trac and SVN.
我们还将LDAP作为Trac和SVN的身份验证机制。
#1
1
We implemented this approach:
我们实施了这种方法:
For Trac you could try Fine Grained Permissions to control access to the wiki pages. Rest of privileges can be managed somehow with standard permissions.
对于Trac,您可以尝试使用细粒度权限来控制对Wiki页面的访问。可以使用标准权限以某种方式管理其余权限。
For the SVN access, you can use the authorization method provided by your server.
对于SVN访问,您可以使用服务器提供的授权方法。
We also have LDAP as authentication mechanism for both Trac and SVN.
我们还将LDAP作为Trac和SVN的身份验证机制。