When working on other things, I found that our coverage tests were failing on master on macOS. I quickly fixed this in certbot/certbot#7972, but there's nothing stopping us from hitting this problem again in the future. I think we should avoid this because it can be a confusing/frustrating experience, especially for new Certbot developers, to investigate test failures on

When singular items are missing we say "does not exist" or doesn't exist".
When singular items are present we say "does exist" or "exists".
Yes, English can be difficult.
https://github.com/acmesh-official/acme.sh/search?q=%22doesn%27t+exists%22&unscoped_q=%22doesn%27t+exists%22
Text says "doesn't exists".

Ref also : https://github.com/acmesh-official/acme.sh/search?q=%22does+not+exists%22&

As #103 showed, we should have clear instructions as to how to add a frontend application inside our NoDock environment.

So, Ubuntu (18.04 at least) installs a cronjob and makes use of renewal-hooks directories. I can't find much documentation about it, but there is a bug report here: https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1706409

There is some documentation on about the renewal-hooks directories:
https://certbot.eff.org/docs/using.html#renewing-certificates

I'm thinking about how I can

Description
certbot-route53.sh has bash-specific features, see #2.

Per documentation:

3. Download the certbot-route53.sh script.
+++
chmod a+x certbot-route53.sh
4. Run the script with your (comma-separated) domain(s) and email address:
sh certbot-route53.sh \
+++

Error
sh certbot-route53.sh ... would fail if sh is not bash-compatible. (for example it's link t

The documentation stresses the Python requests library is needed.

Yet, this plugin is for certbot, which (i) needs requests (ii) relies on acme Python package, which also need requests.

Is there a use case where this plugin could be used standalone without acme/certbot not installed (e.g. for CI purpose)?

References:

• [certbot/setup.py](https://github.com/certbot/certbot/blob/174f