Hi David,
Sorry for the delay. I note that you have set the value of port to 80
but it seems likely that there is already a VirtualHost entry on the
port which is specifying the directory listing for /var/www/. I believe
that debian, like ubuntu, gives you a default site with that property.
If that is right you can either change the port in the script to
something other than 80 or disable the default site entry with:
a2dissite default
apachectl configtest && apachectl graceful
If I have understood the problem correctly, that much should be enough
to get you working. Everything that follows is advice on some ways to
clean up the script a little.
In particular I would recommend that you run the bloodhound_setup.py
script like so:
python bloodhound_setup.py --database-type=$DB --user=$DBUSER
--password=$DBPASSWD --admin-user=$ADMINUSER --admin-password=$ADMINPASSWD
which, if $DBPASSWD is set to the appropriate password for the database,
should provide sensible defaults for everything else and create the
environments directory if required. This should save you from doing this
in the script or providing your own base.ini. So, you will be able to
remove everything from
"###### do I need to sudo or maybe I could just chown -R everything at
the end ??"
to just before
"trac-admin ./bloodhound/environments/main/ deploy ./bloodhound/site #
<- Is this step needed ?"
as that deploy step is definitely needed! The directory specified to
deploy to is not so important but it is reflected in the apache
configuration.
Finally, it may also be worth using "pip install -r requirements.txt"
instead of "pip install -r requirements-dev.txt" as the latter is
intended for developer use.
Hope all that is helpful!
Cheers,
Gary
On 09/06/13 23:27, David Galligani wrote:
I tried installing bloodhound on a new environment (debian) but
still no luck ...
As I see apache does not render python files I think the problem is
in the virtualhost configuration
As I had a warning because mod_wsgi was compiled with a different
version of Python ( 2.7.2 instead of 2.7.3 ) I recompiled
it manually and now I have no warning by Apache .
But still it's not working ...
David
echo "
<VirtualHost *:$PORT>
WSGIDaemonProcess bloodhound_tracker user=$SYSUSER
python-path=$APACHEDIR/bloodhound/installer/bloodhound/lib/python2.7/site-packages
WSGIScriptAlias /bloodhound
$APACHEDIR/bloodhound/installer/bloodhound/site/cgi-bin/trac.wsgi
<Directory $APACHEDIR/bloodhound/installer/bloodhound/site/cgi-bin>
WSGIProcessGroup bloodhound_tracker
WSGIApplicationGroup %{GLOBAL}
Order deny,allow
Allow from all
</Directory>
<LocationMatch "/bloodhound/[^/]+/login">
AuthType Digest
AuthName "Bloodhound"
AuthDigestDomain /bloodhound
AuthUserFile
$APACHEDIR/bloodhound/installer/bloodhound/environments/main/bloodhound.htdigest
Require valid-user
</LocationMatch>
</VirtualHost>
" > /etc/apache2/sites-available/bloodhound
a2ensite bloodhound
apachectl configtest && apachectl graceful
------------------------------------------------------------END-------------------------------------------------------------------------------------------------
