On Wed, 12 Mar 2014 11:47:08 +0100, Saint Germain <[email protected]> wrote :
> Hello, > > I am currently working on an easy way to test/deploy Bloodhound based > on Ansible + Vagrant. > > In theory we just have to do a "vagrant up" and the bloodhound website > should be up and running in a VM. > Or you can use directly the ansible-playbook on a real host to quickly > build your website. > > I choose to work with Debian Wheezy + nginx + uWSGI > > I cannot give a deadline yet as I really don't know how long it will > take me. But if other people are interested, we can share info on this > subject. > > When it is ready it can perhaps be included in the trunk. > It seems that the page on DetailedInstallation is not up-to-date ? https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation Instead of using bloodhound_setup.py I tried using: 1) python ../../createdigest.py --user=admin --password=adminpasswd --realm=bloodhound -f bloodhound.htdigest 2) nano base.ini 3) export DBSTRING=postgres://user:pass@localhost:5432/dbname 4) cd path/to/bloodhound/environments 5) trac-admin main initenv ProjectName $DBSTRING --inherit=path/to/base.ini 6) trac-admin main upgrade 7) trac-admin main wiki upgrade 8) trac-admin main permission add admin TRAC_ADMIN However it seems that the default wiki pages are not loaded because I got a "WikiStart not found" when I try to access the website. I am trying to resolve the same problem as in Trac ticket #11333, which is to re-use an environment directory and only fill the database: http://trac.edgewall.org/ticket/11333 I thought that by using directly the trac-admin commands the the #11333 patch, it would work... Regards,
