fix: update the letsencrypt plugin to run off midnight hours

While ideally this is a custom time, this will help alleviate issues where the letsencrypt certi...

Use `ports` commands in Dockerfile/image section

Fix typo in function name

fix: correct syntax error

Closes #318

fix: use non-deprecated method of retrieving an available port

The old method will be removed in the next Dokku release.

Correct the guard checking if letsencrypt is enabled for an app or not

support wildcard domains

fixes #298

Fix typo in README

Add support for wildcard domains via DNS-01 challenge

Move all config variable usage to the property system

This is necessary due to nginx_restart not being exposed.

This aligns the plugin with how core plugin properties are managed.

This bc-break decreases cognitive load while performing any refactor.

docs: update docs to point out how git:from-image deploys might need changing

If the docker image is built from a Dockerfile that uses an `EXPOSE` directive, proxying may not...

refactor: avoid using a proxied request for the http-01 challenge

Instead, mount a directory that nginx can serve directly.

Closes #291

chore: update letsencrypt image

Fix readme links

Closes #282

Return both host and container config dir

Remove letsencrypt:enable from post-domains-update

Due to order of operations, we add the cert before the router knows the cert is available. Disab...

Fixes #271

Revert "fix: use container-local config dir path when reading arguments"

fix: use container-local config dir path when reading arguments

feat: add letsencrypt:active to check if active

Fix default value in README.md

fix: respect a mapped dokku root when running dokku in a container

Closes #235

feat: re-enable letsencrypt when adding or setting domains

Closes #248

Don't run without domains