On 06/10/2013 01:24 PM, Gary Martin wrote:
Hi David,
Hi Gary
Sorry for the delay.
:) Don't worry ... nobody should works on weekends !
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
Thanks for pointing that out ... but the default virtualhost was alredy
disabled .
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
Thanks ! I will
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.
I put both yesterday :) So I can remove requirements-dev ?
Hope all that is helpful!
It was ! many thanks ... still doesn't run on port 80 ( dunno why ) but
does it run on 8080 ... at least I got it working .
I will continue testing it ( now I have to add ldap auth )
Cheers,
Gary
Cheers
David
