certbot/letsencrypt-auto-source/tests/__init__.py

"""Tests for letsencrypt-auto

Run these locally by saying... ::

    ./build.py && docker build -t lea . -f Dockerfile.<distro> && docker run --rm -t -i lea

"""
Get the first end-to-end test of letsencrypt-auto passing. To run it, cd letsencrypt_auto && ./build.py && docker build -t lea . && docker run --rm -t -i lea So as not to depend on the state of the host machine, the test runs within an Ubuntu Docker image. This lets us sidestep interaction challenges by setting up passwordless sudo. It also lets us insert our own local CA for the mock HTTPS server. (openssl's SSL_CERT_FILE env var replaces rather than adds to the accepted CAs, meaning later connections to PyPI within the same process chain fail. SSL_CERT_DIR seems not to work at all on OS X.) This also demonstrates a way to test across various Linux distros, even within Travis if we like, Also... * Switch to an official release of ConfigArgParse. * Don't redundantly re-bootstrap on --no-self-upgrade (that is, phase 2). 2015-12-17 23:45:51 -05:00			`"""Tests for letsencrypt-auto`

Get le-auto tests running on Travis. 2016-01-08 16:55:52 -05:00			`Run these locally by saying... ::`
Get the first end-to-end test of letsencrypt-auto passing. To run it, cd letsencrypt_auto && ./build.py && docker build -t lea . && docker run --rm -t -i lea So as not to depend on the state of the host machine, the test runs within an Ubuntu Docker image. This lets us sidestep interaction challenges by setting up passwordless sudo. It also lets us insert our own local CA for the mock HTTPS server. (openssl's SSL_CERT_FILE env var replaces rather than adds to the accepted CAs, meaning later connections to PyPI within the same process chain fail. SSL_CERT_DIR seems not to work at all on OS X.) This also demonstrates a way to test across various Linux distros, even within Travis if we like, Also... * Switch to an official release of ConfigArgParse. * Don't redundantly re-bootstrap on --no-self-upgrade (that is, phase 2). 2015-12-17 23:45:51 -05:00
Explicitly add six as a dependency in letsencrypt-auto-source dockerfiles (#5808) * update documentation * explicitly add six as a dependency in letsencrypt-auto-source dockerfiles * pin six version 2018-03-29 18:34:38 -04:00			`./build.py && docker build -t lea . -f Dockerfile.<distro> && docker run --rm -t -i lea`
Get the first end-to-end test of letsencrypt-auto passing. To run it, cd letsencrypt_auto && ./build.py && docker build -t lea . && docker run --rm -t -i lea So as not to depend on the state of the host machine, the test runs within an Ubuntu Docker image. This lets us sidestep interaction challenges by setting up passwordless sudo. It also lets us insert our own local CA for the mock HTTPS server. (openssl's SSL_CERT_FILE env var replaces rather than adds to the accepted CAs, meaning later connections to PyPI within the same process chain fail. SSL_CERT_DIR seems not to work at all on OS X.) This also demonstrates a way to test across various Linux distros, even within Travis if we like, Also... * Switch to an official release of ConfigArgParse. * Don't redundantly re-bootstrap on --no-self-upgrade (that is, phase 2). 2015-12-17 23:45:51 -05:00
			`"""`