Mercurial > libervia-backend
view docker/backend-dev-e2e/certificates/README @ 3539:60d3861e5996
bridge (dbus): use Tx DBus for backend part of D-Bus bridge:
Due to recent SQLAlchemy integration, Libervia is now using AsyncIO loop exclusively as
main loop, thus GLib's one can't be used anymore (event if it could be in a separate
thread).
Furthermore Python-DBus is known to have design flaws mentioned even in the official
documentation.
Tx DBus is now used to replace Python-DBus, but only for the backend for now, as it will
need some work on the frontend before we can get completely rid of it.
| author | Goffi <goffi@goffi.org> |
|---|---|
| date | Thu, 03 Jun 2021 15:21:43 +0200 |
| parents | 73e04040d577 |
| children |
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,libervia-backend.test,libervia-web.test" $ chmod 0644 minica.pem 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.