On Tue, Sep 17, 2013 at 1:25 AM, Jared Duncan <j@jdunk.com&= gt; wrote:

Hi list. =A0I was successfully able to install and run blo= odhound via tracd just fine, but I'm getting a strange 404 situation wh= en I try to access it via apache instead.

I'm using = the same VirtualHost block that was suggested by the installation doc only = with added directives for logging, and a ServerName and port 80 instead of = 8000.

https://issues.apache.org/bloo= dhound/wiki/BloodhoundInstall#WebServer

My= VirtualHost:

<VirtualH= ost *:80>
=A0 =A0= ServerName bh.mydomai= n.com

=A0 =A0 LogLevel warn
=A0 =A0 ErrorLog /var/log/apache2/bh.mydomain.= com-error.log

=A0 =A0 CustomLog /var/log/apach= e2/bh.mydomain.com-access.log combined

=A0 =A0 WSGIDaemonProcess bh_tracker user=3Dbloodhound python-path=3D/u= sr/local/bloodhound/installer/bloodhound/lib/python2.7/site-packages=

=A0 =A0 WSGIScriptAlias /bloodho= und /usr/local/bloodhound/installer/bloodhound/site/cgi-bin/trac.wsgi
=A0 =A0 <Directory /us= r/local/bloodhound/installer/bloodhound/site/cgi-bin>

=A0 =A0 =A0 =A0 WSGIProcessGroup= bh_tracker
=A0 =A0 = =A0 =A0 WSGIApplicationGroup %{GLOBAL}
=A0 =A0 =A0 =A0 Order deny,allow

=A0 =A0 =A0 =A0 Allow from all
=A0 =A0 </Director= y>
=A0 =A0 <Lo= cationMatch "/bloodhound/[^/]+/login">

=A0 =A0 =A0 =A0 AuthType Digest<= /font>
=A0 =A0 =A0 =A0 Auth= Name "Bloodhound"
=A0 =A0 =A0 =A0 AuthDigestDomain /bloodhound

=A0 =A0 =A0 =A0 AuthUserFile /us= r/local/bloodhound/installer/bloodhound/environments/main/bloodhound.htdige= st
=A0 =A0 =A0 =A0 R= equire valid-user

=A0 =A0 </LocationMatch>
</VirtualHost><= /font>

=3D=3D=3D

I = ran trac-admin deploy and restarted apache of course. =A0What happens, thou= gh, is any attempt to access that VirtualHost at any URI for that subdomain= it's configured for yields a 404, and the error log says this:

File does not exi= st: /etc/apache2/htdocs

I know that it&= #39;s matching the VirtualHost block because the above error gets written t= o the very file I uniquely specified in the ErrorLog directive within that = block. =A0(The unique access log gets hit also.)

So... anyone have an idea why it would be looking for a= n "htdocs" directory within /etc/apache2/ instead of /usr= /local/bloodhound/installer/bloodhound/site/ ?

In case it's of any help, mod_wsgi emits the follow= ing "info" messages when apache is started:

<= div>
[info] mod_wsgi (pid=3D15156= ): Attach interpreter ''.

[info] mod_wsgi (pid=3D15156): A= dding '/usr/local/bloodhound/installer/bloodhound/lib/python2.7/site-pa= ckages' to path.

=3D=3D=3D
<= div>

Another thing: the Bloodhound installation doc says:=A0

The user referred = to in the WSGIDaemonProcess should be the user that you wish bloodhound to = be run as and so that user must have the appropriate set of permissions to = access the Bloodhound installation. Running with any special system level p= rivileges should not be required and is not recommended.

...but it says nothing whatsoever about wh= ich permissions are needed on which files/directories, so we are left to co= mpletely guess, and doing something like=A0

sudo chown -R bloodhound.www-data /usr/loca= l/bloodhound; sudo chmod -R ug+rwx /usr/local/bloodhound

...is ugly, inconvenient, and overly-permissive at best= , and breaks things at worst. =A0Is there a better way?