You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`CERTBOT_STAGING` (default: `0`) set to `1` to use Let's Encrypt staging
60
+
-`CERTBOT_FORCE_BOOTSTRAP` (default: `0`) set to `1` to force re-running initial certificate issuance
61
+
-`CERTBOT_RELOAD_COMMAND` optional command run after successful renewals (for reverse proxies/web servers)
62
+
63
+
#### Hosting-location behavior
64
+
-**AWS EC2 / container hosts**: startup scripts detect AWS environments and request certificates with Certbot automatically.
65
+
-**Heroku**: startup scripts detect Heroku and skip Certbot because SSL is managed by Heroku ACM.
66
+
67
+
At startup, the bootstrap script checks for an existing certificate at `/etc/letsencrypt/live/<domain>/fullchain.pem`.
68
+
If it is missing, initial Certbot setup runs automatically; otherwise it skips issuance and keeps renewal-only behavior.
69
+
70
+
#### Manual commands
71
+
- Initial setup: `sh deploy/certbot/bootstrap.sh`
72
+
- Renewal run: `sh deploy/certbot/renew.sh`
73
+
74
+
> Renewal scheduling writes to `/etc/cron.d/certbot-renew` and uses root because Certbot certificate files are stored under `/etc/letsencrypt`; renewal output is sent to syslog with the `certbot-renew` tag.
0 commit comments