| Age | Commit message (Collapse) | Author |
|---|
|
I would like the message expiry to be very long, so that there is very little
chance of users not being able to retrieve messages.
|
|
This commit enabled SOCKS5 Bytestreams, allowing users to send and receive
files.
|
|
Previously, the playbook would fail if it needed to install packages, as this
(in the case of apt) requires sudo.
|
|
At present, these are not automated by the runbook and need to be manually run
as part of setup for each new managed host the playbook is run against.
|
|
This directory is created by a user command, not as part of the package
installation process. Therefore, it may not exist if the user has not yet
configured borgmatic on the host.
|
|
This commit uses the simpler, more standard validate feature of template
instead of triggering a handler. The feature is there - may as well use it!
|
|
This commit adds borgmatic, to provide automated backups.
|
|
For now, there are not too many variables to set per host. However, this will
likely change in future commits, with a greater number of variables needing to
be configured. Therefore, this commit encourages the user to define these
variables in a yaml file, which will be more cleanly scalable.
|
|
I may in the future introduce yaml config file templates, since this is a
relatively common format for configuring services. If I do so, I should ensure
that yamllint gets run on these too.
|
|
This commit adds some basic DNS instructions for the initial setup of the host,
which can be used when the domain of the JID matches the domain of the host.
|
|
The playbook previosuly assigned the prosody config files to the root group.
With root as the owner, and permissions as 0640, this meant that prosody was
not able to read the files. This commit fixes this.
|
|
This commit ensures certificates are installed, via Lets Encrypt.
|
|
There is no sense reloading prosody if none of its configuration files have
changed. Therefore, this commit moves the reload to a handler that only gets
triggered in this situation.
|
|
There are some checks that are enabled by default in yamllint, that are not
caught by default by ansible-lint. For instance, ansible-lint does not check
for line lengths in its default configuration. Therefore, we would like to
re-introduce yamllint to make sure we do not miss any checks.
|
|
ansible-lint uses yamllint under the hood, and also checks for many more
"logical" errors in the ansible config.
|
|
I would like to avoid accidentally committing one of these files.
|
|
This commit uses the new per-host virtual_host variable to create the necessary
prosody host-specific cfg files.
|
|
This commit adds a prosody configuration file that can be installed on the
remote hosts. This lets me make the configuration locally, deploy it to staging
environments, and then to prod, without having to directly login to the hosts.
|
|
This commit enables the necessary ports for XMPP, web hosting (to allow certbot
to renew automatically) and SSH.
|
|
At present, the playbook simply ensures that all required packages are
installed.
|
|
This project is licensed under AGPL-3.0-only. I would like to use reuse across
this project, therefore the license is placed in the LICENSES directory.
|
