2 Commits

Include renames

Author	SHA1	Message	Date
bitdeals	36e1865e37	feat: CERTBOT_DOMAIN may name several domains ... certbot's own -d already takes a comma-separated list and puts every name in the certificate's Subject Alternative Names, so `-d "$CERTBOT_DOMAIN"` needed no change at all. What assumed a single domain was everything that treated the variable as a *file name*: --cert-name, and the two scripts that address the lineage under /etc/letsencrypt/live. Certbot names a lineage after the first domain of the list, so all three now take ${CERTBOT_DOMAIN%%,*} instead of the whole string -- otherwise a two-domain value asks for a lineage literally called "a.org,b.org" and the renewal pass looks for a directory nobody made. One certificate with several names rather than several lineages: HAProxy binds a single site.pem, and a second lineage would have nowhere to go. Adding a domain to CERTBOT_DOMAIN on a machine that already holds a certificate still needs one manual issuance -- `certbot renew` reads the names off the certificate it has and never looks at the variable. The README says so, and gives the command.	2026-08-20 11:53:12 +00:00
bitdeals	55083856c1	docs: add README in English and Russian ... Same structure as the bitmessage and bitcoind repositories. The notes carry what the scripts cannot say for themselves: that the first certificate is a self-signed placeholder and stays one if issuance fails, that a refused installation is reported but cannot be repaired, that the scripts are sourced rather than executed so working directory and set -e are inherited, and that a stop during issuance can outlast docker's grace period.	2026-08-07 13:39:55 +00:00