permacomputing

commit d334a5c0dbafe50e42e0ad2539b3544be92016bd
parent be4703cdea825f556a2f8c55db0766ef50662402
Author: spacehobo <spacehobo@web>
Date:   Sun, 10 May 2026 19:14:01 +0200

Possible one-liners to avoid errors.

Diffstat:
M
eik.mdwn
 | 
5
+++++

1 file changed, 5 insertions(+), 0 deletions(-)
diff --git a/eik.mdwn b/eik.mdwn
@@ -90,6 +90,11 @@ We use `acme.sh` for handling certs, however expanding certs with a new domain i
     --fullchain-file /etc/nginx/certs/cert.pem \
     --reloadcmd "systemctl force-reload nginx"
 
+This can be automated by adding the new domain to the `Le_Alt` line of `eik.permacomputing.net_ecc/eik.permacomputing.net.conf` and running something like the following:
+
+    acme.sh --issue --nginx $(acme.sh --list | awk '$1 == "eik.permacomputing.net" {split($3,names,",");for(name in names){ printf "-d %s ", names[name]}}')
+    acme.sh --install-cert $(acme.sh --list | awk '$1 == "eik.permacomputing.net" {split($3,names,",");for(name in names){ printf "-d %s ", names[name]}}')     --key-file /etc/nginx/certs/key.pem --fullchain-file /etc/nginx/certs/cert.pem --reloadcmd "systemctl force-reload nginx"
+
 Our `acme.sh` makes use of letsencrypt CA servers, as the default one from ZeroSSL keeps on being fussy. The setting was changed like this:
 
     acme.sh --set-default-ca --server letsencrypt