On Nov 8, 2006, at 3:16 PM, solo turn wrote: > > what are the main features of tracforge?
All the stuff I mentioned in the email. Trac-to-trac data subscriptions, centralized permissions and roles, and SSO. Other features are planned, but not finished yet. --Noah > > On 10/18/06, Noah Kantrowitz <[EMAIL PROTECTED]> 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 >> --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
