4 Commits

Include renames

Author	SHA1	Message	Date
bitdeals	0801b0d376	feat: put the log in the volume, so the container can be read-only ... /var/log/letsencrypt was the only thing this image wrote outside its volumes, and it is what stopped `read_only: true` from working. --logs-dir moves it to /etc/letsencrypt/logs, beside the account key and the renewal config it already keeps there. The second gain is the one that matters more here. This is the service whose breakage does not announce itself: a renewal that stops working is an expired certificate sixty days later, and the log is what says why. On the root filesystem it died with every container the registry replaced; in the volume it outlives them. Nothing else about the container needs to change to be confined. It never changes user, the files it touches are its own, the ACME challenge is served on 380 rather than a privileged port, and the HAProxy runtime socket it writes to is group-owned by root -- so it reaches it by permission rather than by CAP_DAC_OVERRIDE, and `cap_drop: ALL` takes nothing away. Measured on the live relay: no file under /etc/letsencrypt or /etc/certificates is owned by anyone but root, and the socket is srw-rw---- 1001:0. Both READMEs say what a caller should set now, stop_grace_period included -- the entrypoint has asked for that one since it was written.	2026-09-10 11:49:04 +00:00
bitdeals	e8204bbb4d	fix: the certificate follows CERTBOT_DOMAIN, on every pass ... A pass branched on whether /etc/letsencrypt/live/<first-name> existed: present, it ran `certbot renew`; absent, it handed over to the creation script. Only the second path was ever told the names to ask for, so after the first issuance CERTBOT_DOMAIN stopped reaching certbot altogether -- renew takes the names off the certificate it already holds. Editing the variable did nothing, silently, and the README documented the manual issuance needed to work around it. The branch is gone. Every pass now runs certonly with the names spelled out, and certbot decides what that means: same names, not due -> "Certificate not yet due for renewal; no action taken", no connection opened, nothing spent against the rate limits name added or removed -> reissued with exactly the requested set due for renewal -> renewed --keep-until-expiring is what makes the first line true, and --cert-name (already passed) is what keeps a changed list updating the existing lineage instead of starting a second one beside it. No --expand is needed to add a name once the lineage is named. All three decisions were checked against the live stands: the no-op one with a real run on testnet2, the other two as dry runs on testnet1 and testnet2. With the branch removed, 1-renew-cert.sh is a pass-through and the numbering finally matches the order things run in -- 0-create-cert.sh used to execute after 1-renew-cert.sh. So: 1-renew-cert.sh deleted, 0-create-cert.sh renamed to 1-ensure-cert.sh, which is what it now does. Claude-Session: https://claude.ai/code/session_01BvgYcYPWd1KGABLKViVPSk	2026-08-24 13:13:03 +00:00
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