Hi,
According to the discussion we just had on #soju, here is a quick and
dirty draft of a documentation that may help future soju hosters get the
correct certificate at the correct path.
Best,
neogaldr (1):
Add certbot instructions.
contrib/certbot.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 contrib/certbot.md
--
2.38.4
On Fri Mar 24, 2023 at 4:41 PM CET, ~martylake wrote:
> From: neogaldr <neogaldr@gmail.com>>> ---> contrib/certbot.md | 21 +++++++++++++++++++++> 1 file changed, 21 insertions(+)> create mode 100644 contrib/certbot.md>> diff --git a/contrib/certbot.md b/contrib/certbot.md> new file mode 100644> index 0000000..e386a49> --- /dev/null> +++ b/contrib/certbot.md> @@ -0,0 +1,21 @@> +# Certbot> +> +After following the instructions of certbot to generate a certificate> +for your domain (here `example.org`), copy the `fullchain.pem` and> +the `privkey.pem` next to your config file.> +> +```sh> +$ cp certbot-data/live/example.org/fullchain.pem soju-data/cert.pem> +$ cp certbot-data/live/example.org/privkey.pem soju-data/key.pem> +```
to bikeshed this a little (unrelated to soju itself)- half the point of setting
up certbot is to get *automated* certificate renewal.
but since this manually copies the certificate, it will not automatically renew,
and will eventually expire without you copying a new one over it?
> +> +> +# Config file> +> +Make sure the config file has these directives:> +> +```> +listen ircs://> +tls cert.pem key.pem> +hostname example.org> +```> -- > 2.38.4