#796: Vagrant deployment with Ansible provisioning
-------------------------+-------------------------------------------------
Reporter: | Owner: nobody
SaintGermain | Status: new
Type: | Milestone:
enhancement | Version: 0.8.0dev
Priority: minor | Keywords: test vagrant ansible provisionig vm
Component: installer |
Resolution: |
-------------------------+-------------------------------------------------
Comment (by SaintGermain):
Preliminary patch available on my Bitbucket repository:
https://bitbucket.org/saintgermain/bloodhound-mq/branch/t796_vagrant
Note:
* I had to use a workaround for ticket #795
* It uses a VM downloaded from http://basebox.libera.cc/debian-
wheezy-64.box (use at your own risk or create your own)
* Idempotency may be a problem as the Ansible script always try to create
the database and the environment
* I haven't tested what happen when we modify the Bloodhound source code
or templates and run it again. It may be a good idea to include an option
in the future to install in dev mode.
* I am not sure at all of what I have done with uWSGI, especially with
uwsgi_params, comments welcome !
* There may be a problem with Unicode/Ascii in PostgreSQL database
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/796#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
