system-config/playbooks/roles/letsencrypt-create-certs
Jeremy Stanley f477e35561 Upgrade to Keycloak 23.0
This includes a switch from the "legacy" style Wildfly-based image
to a new setup using Quarkus.

Because Keycloak maintainers consider H2 databases as a test/dev
only option, there are no good migration and upgrade paths short of
export/import data. Go ahead and change our deployment model to rely
on a proper RDBMS, run locally from a container on the same server.

Change-Id: I01f8045563e9f6db6168b92c5a868b8095c0d97b
2024-02-06 05:33:37 +00:00
..
defaults Fix letsencrypt_self_generate_tokens defaults 2021-10-06 08:40:43 -07:00
handlers Upgrade to Keycloak 23.0 2024-02-06 05:33:37 +00:00
tasks Generate ssl check list directly from letsencrypt variables 2020-05-20 14:27:14 +10:00
README.rst letsencrypt : don't use staging in the gate 2021-10-06 15:34:21 +11:00

README.rst

Generate letsencrypt certificates

This must run after the letsencrypt-install-acme-sh, letsencrypt-request-certs and letsencrypt-install-txt-records roles. It will run the acme.sh process to create the certificates on the host.

Role Variables

The same variable as described in letsencrypt-request-certs.