[Agaric-specific] Set up a Trac issue queue for a project
Visitors, please note that while Agaric-specific documentation may be informative to you, it is meant primarily for Agaric's internal use and is highly unlikely to work step-by-step without fulfilling an awful lot of dependencies first.
After setting up the project per Deploying the Agaric way, we can use our trac setup vlad task to do most of the work.
From within the project:
rake test vlad:setup_trac
This sets up trac and adds all current Agarics to the trac admin role for the project. There is still one thing we have to do to get it working with automatic login (which piggybacks on webauth and is the only option for login).
On the test server, ssh simone.mayfirst.org, we edit the Apache groups file if we want to have access for non-agaric group members:
sudo vi /etc/apache2/groups
example: personx persony personz
We need to set up access control for this trac installation.
sudo vi /etc/apache2/sites-enabled/agariclabs.net
And add below the list of trac entries like this, another entry like this:
<Location "/trac/example">
AuthType WebAuth
AuthGroupFile groups
require group agaric example
</Location>
where example is replaced by our project's name.
This authorization setup isn't optional; Trac is integrated with the Webauth login and this is the only way users can log in to the Trac project.
And then don't forget to reload Apache's configuration:
sudo apache2ctl restart
For more detail about the require group line, see Adding a Kerberos user to a group and creating a Kerberos user.
Comments
Post new comment