view docker/backend_e2e/certificates/README @ 3415:814e118d9ef3

tests: end-2-end tests first draft: - e2e tests are launched inside the new docker e2e test environment - `run_e2e.py` launch the docker container, mount the current code base in it, launch the e2e tests and print report in real time - `conftest.py` are pytest fixtures managing many things such as account creation, fake files management, JSON or Domish.Element parsing, fake editor, etc. - `test_jp.py` are end-to-end test done with `jp`. `sh` library is used to make tests writting as user-friendly as possible. The `SAT_TEST_ENV_E2E` environment variable is checked, and tests will be skipped if it's not set.
author Goffi <goffi@goffi.org>
date Thu, 12 Nov 2020 14:53:16 +0100
parents 127dde80a0a5
children 829fee174606
line wrap: on
line source

Those certificates are used to activate TLS for end-2-end testing (to be as
close as possible as production environment), they are used in other containers
needing TLS certificates (notably Prosody).

To generate them, minica has been used. Minica can be found at https://github.com/jsha/minica.

The following commands have been used:

$ minica --domains "server1.test,*.server1.test,server2.test,server3.test,sat.test"
$ chmod 0644 minica.pem
$ chmod 0644 server1.test/cert.pem
$ chmod 0640 server1.test/key.pem

Note that certificates are valid for 2 years and 30 days, so they must be renewed after this delay.