DAG to renew certificates with acme.sh

acme_renew/Makefile

@@ -0,0 +1,92 @@
+WD=/var/lib/dags/acme_renew
+
+.PHONY: all refresh_pg renew_certs
+
+NGINX_RELOAD=$(WD)/nginx_reload
+
+all: renew_certs $(NGINX_RELOAD) refresh_pg
+
+###############################################################################
+
+CERTS_PATH=/mnt/certs/acme
+
+MONOTREMATA_DOMAIN=monotremata.xyz
+MONOTREMATA_PATH=$(CERTS_PATH)/$(MONOTREMATA_DOMAIN)
+MONOTREMATA_CERT=$(MONOTREMATA_PATH)/fullchain.cer
+MONOTREMATA_KEY=$(MONOTREMATA_PATH)/$(MONOTREMATA_DOMAIN).key
+
+NARWHAL_DOMAIN=narwhal.monotremata.xyz
+NARWHAL_PATH=$(CERTS_PATH)/$(NARWHAL_DOMAIN)
+NARWHAL_CERT=$(NARWHAL_PATH)/fullchain.cer
+NARWHAL_KEY=$(NARWHAL_PATH)/$(NARWHAL_DOMAIN).key
+
+CALADAN_DOMAIN=caladan.monotremata.xyz
+CALADAN_PATH=$(CERTS_PATH)/$(CALADAN_DOMAIN)
+CALADAN_CERT=$(CALADAN_PATH)/fullchain.cer
+CALADAN_KEY=$(CALADAN_PATH)/$(CALADAN_DOMAIN).key
+
+XMPP_DOMAIN=xmpp.monotremata.xyz
+XMPP_PATH=$(CERTS_PATH)/$(XMPP_DOMAIN)
+XMPP_CERT=$(XMPP_PATH)/fullchain.cer
+XMPP_KEY=$(XMPP_PATH)/$(XMPP_DOMAIN).key
+
+###############################################################################
+# Renew the certificates using acme.sh. Because `renew_certs` is a phony
+# target, it will be run each time, but the certificate files will only be
+# updated if a renewal happens
+
+$(MONOTREMATA_CERT): renew_certs
+$(MONOTREMATA_KEY): renew_certs
+$(NARWHAL_CERT): renew_certs
+$(NARWHAL_KEY): renew_certs
+$(CALADAN_CERT): renew_certs
+$(CALADAN_KEY): renew_certs
+$(XMPP_CERT): renew_certs
+$(XMPP_KEY): renew_certs
+
+ACMESH_COMPOSE_FILE=/srv/services/acmesh/docker-compose.yml
+
+RENEW_CMD="/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" --config-home "/acme.sh"
+
+renew_certs:
+	docker-compose \
+		--file $(ACMESH_COMPOSE_FILE) \
+		run --rm acmesh \
+		$(RENEW_CMD)
+
+###############################################################################
+# Reload the nginx instance running on my reverse proxy docker-compose service
+# so that it uses the new certificates.
+# The target is just an empty sentinel target with no meaningful data other
+# than its modification date.
+# So far, the nginx instance running on `narwhal` only uses the `monotremata`
+# and `narwhal` certificates, so it only needs to be reloaded if those are
+# updated
+
+NGINX_COMPOSE_FILE=/srv/services/reverse_proxy/docker-compose.yml
+
+$(NGINX_RELOAD): $(MONOTREMATA_CERT) $(MONOTREMATA_KEY) $(NARWHAL_CERT) $(NARWHAL_KEY)
+	mkdir -p $(@D)
+	docker-compose \
+		--file $(NGINX_COMPOSE_FILE) \
+		exec nginx \
+		nginx -s reload
+	touch $@
+
+###############################################################################
+# Copy the certificate for the postgresql domain to the folder where postgre
+# service expects it
+
+PG_SSL_PATH=/mnt/docker_volumes/postgres/ssl
+PG_CERT=$(PG_SSL_PATH)/server.crt
+PG_KEY=$(PG_SSL_PATH)/server.key
+
+$(PG_CERT): $(MONOTREMATA_CERT)
+	mkdir -p $(@D)
+	rsync --copy-links $< $@
+
+$(PG_KEY): $(MONOTREMATA_KEY)
+	mkdir -p $(@D)
+	rsync --copy-links $< $@
+
+refresh_pg: $(PG_CERT) $(PG_KEY)

acme_renew/README.md

@@ -0,0 +1,16 @@
+# acme renew
+
+This DAG renews wildcard certificates using `acme.sh`.
+
+If a renewal happens, reload the nginx instance and deploy certificates to the
+PostgreSQL instance.
+
+The Nginx instance has the actual certificate files mounted as read-only
+mounts, so it doesn't need any explicit deployment, just a reload.
+
+PostgreSQL complains if the certificates are mounted as read-only, so I opted
+for making a copy of the files to volume used by PostgreSQL because I don't
+like mouting the actual original files with write permissions to any container
+other than the acme.sh one.
+On the other hand, PostgreSQL doesn't need to be reloaded to pick the new
+files.