Hi,
I've been having a quick look at getting some quick instructions
together for installing more or less from scratch using nginx as the
webserver and making use of gunicorn to run trac as a wsgi application.
The results of this so far are here:
https://issues.apache.org/bloodhound/wiki/BloodhoundInstallNginx
As far as I can tell, the instructions work for the last release but
there may be issues with staying authenticated on trunk. I'll look into
this further in a bit to see if there are any tickets to raise for us.
Otherwise, if anyone wants to make improvements to the instructions,
that would be great.
Has anyone tried MySQL recently with Bloodhound?
Cheers,
Gary
On 16/04/13 18:43, Joe Dreimann wrote:
On 16 Apr 2013, at 18:31, Ryan Ollos <[email protected]> wrote:
On Tue, Apr 16, 2013 at 9:07 AM, Olemis Lang <[email protected]> wrote:
As a side note to this thread in the last few days there are a
significant number of messages about Bloodhound sent to trac-users ML
(which is nice ... USERS ... hehe ! ;) . I've noticed that only
@rjollos and me have ever replied . So maybe it's a good idea to
subscribe to that list too (if not already done) and browse list
archive for recent messages . Alternately we could activate
[email protected] too .
Summarizing users have been requesting :
- Migration from Trac>=0.11 to Bloodhound
- MySQL as DB backend
- Installation procedure using nginx
- Documentation about all this .
I believe our list is called [email protected], not users@ and it is already active, I
am subscribed to it at least.
- Joe
I'm not sure if there is a good way to move the discussion over to a
Bloodhound mailing list from the start, but I tried CC'ing
[email protected] on a post just now and it seems to have at least
gone through.
Perhaps we can CC dev@ or users@ on the first reply, and ask users to
subscribe to the bloodhound.apache.org list and then remove
[email protected] on their first subsequent "reply all".
