<feed xmlns='http://www.w3.org/2005/Atom'>
<title>acme/install-for-prosody, branch master</title>
<subtitle>Tiny wrapper around Lego to handle automatic cert renewal.
</subtitle>
<id>https://git.fennell.dev/acme/atom?h=master</id>
<link rel='self' href='https://git.fennell.dev/acme/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.fennell.dev/acme/'/>
<updated>2024-05-29T17:16:11Z</updated>
<entry>
<title>Generalise prosody-specific install script</title>
<updated>2024-05-29T17:16:11Z</updated>
<author>
<name>Matthew Fennell</name>
<email>matthew@fennell.dev</email>
</author>
<published>2024-05-29T17:16:11Z</published>
<link rel='alternate' type='text/html' href='https://git.fennell.dev/acme/commit/?id=a960b23caebd5362b5f292f73c6e41ebee2ad98c'/>
<id>urn:sha1:a960b23caebd5362b5f292f73c6e41ebee2ad98c</id>
<content type='text'>
This project's initial purpose was to automatically renew certiricates across
multiple prosody servers. However, over time, it has been used with more
services, each with their own ad-hoc and custom installation scripts.

This commit replaces the install-for-prosody script with a more general script
that can handle multiple different kinds of services in the future.
</content>
</entry>
<entry>
<title>Initial commit</title>
<updated>2024-02-28T21:40:21Z</updated>
<author>
<name>Matthew Fennell</name>
<email>matthew@fennell.dev</email>
</author>
<published>2024-02-28T19:17:25Z</published>
<link rel='alternate' type='text/html' href='https://git.fennell.dev/acme/commit/?id=d7e965843eb32fc2e459a15fe70251964ff40394'/>
<id>urn:sha1:d7e965843eb32fc2e459a15fe70251964ff40394</id>
<content type='text'>
This commit adds the initial structure / scaffolding on which the rest of the
project can be built.

The idea is to have an entry point written in python, which parses a toml file
which contains information about each domain, and general configuration of the
lego tool which will actually renew the certificates. Each domain has an
additional post-renew script, the path to which is given in the config file,
which is used to install the new certificates onto the remote hosts if
necessary.
</content>
</entry>
</feed>
