apache with mod_wsgi takes care of starting the app.
If the role is first ran with the defaults, the ara systemd service
will be running.
If we re-run the role and choose an apache deployment, we need to make
sure we're disabling it.
What this boils down to -- let's always set up the systemd service
but start it or disable it according to what we need to deploy.
Change-Id: I8fceed417d766a28564ad88a972de4f38c1b44ac
We were not reloading or restarting ara after changing
the parameters.
This means that running a second time with different
parameters will not be effective automatically.
Also, in order to be effective, the unit file we setup
needs to be in /etc/systemd, not /usr/lib/systemd.
Change-Id: I53716fc2bdb7cf8afc2c5ea39ab953a51c9c4585
- split embedded and apache configuation in separate files
- use systemd to launch and enable httpd or embedded server
- remove unused handler
Change-Id: I25c92b2b38125826087957fb8ce9320641cf86f0
- Add copyright headers (sorry)
- Re-order tasks
- Add missing wsgi required packages
- Use template instead of file for default ansible.cfg
- Use handler to restart apache if need be
- Use command instead of shell unless necessary
- Fix mistakes in systemd service
- Fix mistakes in debian family required packages
- Add friendly instructions at the end of the setup
- Improve README
Change-Id: I84d59facfdc593bc82ac1d1436a49f85c2d1637b