ansible/test/utils/docker/httptester
Matt Martz 9048cf2758 Changes to the httptester docker image to support new client cert functionality in tests (#19912)
* Fix Dockerfile
* Add changes to docker image to support new client cert functionality
* Update repo:tag for docker
2017-01-04 21:07:13 -08:00
..
Dockerfile Changes to the httptester docker image to support new client cert functionality in tests (#19912) 2017-01-04 21:07:13 -08:00
httptester.yml Changes to the httptester docker image to support new client cert functionality in tests (#19912) 2017-01-04 21:07:13 -08:00
nginx.sites.conf Changes to the httptester docker image to support new client cert functionality in tests (#19912) 2017-01-04 21:07:13 -08:00
packer.json Changes to the httptester docker image to support new client cert functionality in tests (#19912) 2017-01-04 21:07:13 -08:00
README.rst Changes to the httptester docker image to support new client cert functionality in tests (#19912) 2017-01-04 21:07:13 -08:00
services.sh

httptester
==========

HTTP Testing endpoint which provides httpbin, nginx, SSL and SNI
capabilities, for providing a local HTTP endpoint for testing

Building
--------

Docker
~~~~~~

Both ways of building docker utilize the ``nginx:alpine`` image, but can
be customized for ``Fedora``, ``Red Hat``, ``CentOS``, ``Ubuntu``,
``Debian`` and other variants of ``Alpine``

When utilizing ``packer`` or configuring with ``ansible-playbook``
the services will not automtically start on launch, and will have to be
manually started using::

    $ /services.sh

Such as when starting a docker container::

    docker run -ti --rm -p 80:80 -p 443:443 --name httptester ansible/ansible:httptester /services.sh

docker build
^^^^^^^^^^^^

::

    docker build -t ansible/ansible:httptester .

packer
^^^^^^

The packer build will use ``ansible-playbook`` to perform the
configuration, and will tag the image as ``ansible/ansible:httptester``

::

    packer build packer.json

Ansible
~~~~~~~

::

    ansible-playbook -i hosts -v httptester.yml