I have just installed Agilo for Trac. So far so good. I'm going through the motions of the eval of the FOSS version right at the moment to see if it makes Trac do more of what we need it to do- if it passes muster, we'll evaluate whether we need the PRO version or not.
However, there's a couple of gotchas I've tripped across getting it up and running:
I'm doing a WSGI install for the setup. As soon as you turn on Agilo, you force a theme on Trac, breaking everything. Someone needs to document that you need to copy the contents of agilo/htdocs into your WSGI htdocs under agilo/ for everything to keep working right.
The other gotcha out of the gate is that your link for Admin needs to not be there or needs to redirect to something sane if the person's not authenticated. Trac+Agilo goes off into the weeds with that link until you authenticate yourself; Trac hides and shows an Admin tab depending on permissions of the person on the page at a given time.
On 14/mar/2012, at 11:13, Stefano Rago wrote:
>>
>> I'm doing a WSGI install for the setup. As soon as you turn on Agilo, you force a theme on Trac, breaking everything. Someone needs to document that you need to copy the contents of agilo/htdocs into your WSGI htdocs under agilo/ for everything to keep working right.
>
> You are right, the whole install documentation has room for improvement. I took note of that.
I have found this link which might be helpful for you:
http://trac.edgewall.org/wiki/TracModWSGI#Recommendedtrac.wsgiscript
among other things, "trac-admin deploy" takes care of deploying the static content from trac and all its plugins as well.
Hope this helps
Cheers
Stefano Rago