Now that ara-{clients,server,plugins} have been merged back into
ara, it's easier to keep everything in the same repository.
The roles and integration tests have already been moved to the ara
repository so we can remove this now.
Change-Id: I8baf5701abb4bd030c5f0b321790482e0f9c229b
This wasn't caught in the integration tests because it is presumably
included in the image we were using. Ansible will complain that it can't
find a virtualenv binary if it isn't installed.
Also work around the fact that the virtualenv packages are excluded
in the dnf configuration.
Change-Id: Id1bc861c99d04dad4d9c6b366b680e00e6891db7
These are largely imported from the existing ARA 0.x integration
tests. Ideally, both 0.x and 1.0 would be using the same tests and
jobs to test themselves.
This effectively adds three jobs:
- ara-integration-fedora-2.7
- ara-integration-fedora-devel
- ara-integration-ubuntu-2.6
These jobs install Ansible from source and then installs ara-server,
ara-clients and ara-plugins in a virtualenv. It then runs the
integration-tests.yaml playbook.
Change-Id: Id0e78259a2bc69f66bc68a9c528613e4d5b7c2a4
This adds a role which:
- Sets up user/group/logging for Hugo
- Retrieves and installs the hugo from upstream release
- Sets up a systemd unit file to keep the hugo server running
- Installs and configure nginx as a reverse proxy to the hugo server
to serve ara.recordsansible.org
I'm not sure yet if keeping the hugo server running is the way to
go or if we should regenerate the static files every time.
It sort of goes against the point of hugo to use the server but
the fact that it reloads automatically when the source changes could
come in handy for automated updates.
Change-Id: I40e833a27117f9ec5003007bb08a677e16734e55
David Moreau Simard