Hi everyone,
I've been trying to set up tracforge as per the instructions below, but
have come up with the following error:
"Cannot find an implementation of the "IPermissionStore" interface
named "TracForgePermissionModule".'
>From what I can tell, the TracForge egg is in the right place (under
<pythonlib>/site_packages/) and is being loaded. (When I put a second
copy under my tracforge master evironment's plugin directory, I get a
notice saying that the TracForge egg has already been loaded from the
global location when running trac-admin commands.) Should this egg be
located elsewhere? Am I supposed to run a certain command after
installing the TracForge egg and configuring the master environment?
I am running this on FreeBSD 6.1 with Python 2.4.3 and am using Apache
and mod_python as a web server. The configuration is as follows the
full traceback below. Note that I have configured the site as a virtual
host.
Any help would be much appreciated.
Thanks,
Mark
Traceback (most recent call last):
File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line
356, in dispatch_request
dispatcher.dispatch(req)
File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line
190, in dispatch
req.perm = PermissionCache(self.env, req.authname)
File "/usr/local/lib/python2.4/site-packages/trac/perm.py", line 267,
in __init__
self.perms = PermissionSystem(env).get_user_permissions(username)
File "/usr/local/lib/python2.4/site-packages/trac/perm.py", line 231,
in get_user_permissions
for perm in self.store.get_user_permissions(username):
File "/usr/local/lib/python2.4/site-packages/trac/config.py", line
377, in __get__
raise AttributeError('Cannot find an implementation of the "%s" '
AttributeError: Cannot find an implementation of the "IPermissionStore"
interface named "TracForgePermissionModule". Please update the option
trac.permission_store in trac.ini.
Apache:
<VirtualHost host.org >
DocumentRoot /usr/local/www/tracforge/
ServerName host.org
<Location /tracforge>
SetHandler mod_python
PythonHandler trac.web.modpython_frontend
PythonOption TracEnv /usr/local/www/tracforge
PythonOption TracUriRoot /tracforge
PythonDebug on
Allow from all
</Location>
<LocationMatch "[^/]+/login">
AuthType Basic
AuthName "TracForge"
AuthUserFile /usr/local/www/tracforge/htdocs/.htpasswd
Require valid-user
</LocationMatch>
</VirtualHost>
Noah Kantrowitz wrote:
> Okay, this is a general overview of how to setup what is currently
> working of TracForge.
>
> First designate one env to be the master. This will manage SSO, and
> hold the central roles and permissions. This is also commonly the
> aggregate trac if you are using the data subscription system, but it
> doesn't need to be.
>
> On each Trac, including the master, set the master_path option (under
> [tracforge]) to the full filesystem path to the master env.
>
> On the master env, activate these components:
> tracforge.* = enabled
> tracforge.linker.* = disabled
> tracforge.linker.auth.tracforgecookiemunger = enabled
> tracforge.subscriptions.* = disabled
>
> On each client env activate these:
> trac.web.auth.loginmodule = disabled
> tracforge.admin.perm.* = enabled
> tracforge.linker.auth.* = enabled
>
> For all envs set this in [trac]:
> permission_store = TracForgePermissionModule
>
> That should be all config changes you need. If you want to use the
> data subscription system, just enable tracforge.subscriptions.* on
> all envs.
>
> To setup the tracforge system, go into WebAdmin on the master, and
> there should be a TracForge Project Admin screen. In there add each
> of your projects. For now TracForge cannot actually create the
> projects, so make them the normal way and then just enter them into
> TracForge. Once that is done you should be able to add central roles
> and permissions. Permissions work exactly the same way as normal,
> with the central ones combined with the per-project permissions.
> Roles show up as groups, so you can do something like give the group
> "member" the permission WIKI_MODIFY, and then add some users as
> members to a project. The "*" project on the roles screen means that
> user will have the given role on all projects (very handy for
> configuring global admin accounts).
>
> There isn't much configuration to the subscription system. It should
> autodetect all sibling envs (envs sharing the same enclosing folder),
> and let you add subscriptions from one env to another. Changesets
> work very well, and tickets are mostly working (though there is no
> support for attachments yet).
>
> Thats about all I can think of as far as setting up tracforge. Let me
> know if you have further questions.
>
> --Noah
>
> On Oct 17, 2006, at 10:14 AM, Michal Bielicki wrote:
>
> >
> > I installed tracforge today. Install was painless, adding the config
> > values was painless, creating a master project as well. My problem is
> > .... now what ?
> >
> > :)
> > cheers
> >
> > Michal
> > --
> > Michal Bielicki
> > CEO
> > VoiceWorks Sp. z o.o.
> > http://www.voiceworks.pl/
> > Voice: +48 22 875 32 93
> > Fax: +48 22 875 32 94
> >
> >
> > >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/trac-users
-~----------~----~----~----~------~----~------~--~---
