xmpp-prosody-ansible-deploy/Makefile, branch masterAnsible playbook that deploys prosody to a server.
https://git.fennell.dev/xmpp-prosody-ansible-deploy/atom?h=master2026-01-02T13:16:35ZDefine all hosts in a single inventory2026-01-02T13:16:35ZMatthew Fennellmatthew@fennell.dev2026-01-02T13:16:35Zurn:sha1:c1a5a58d20488272bf0bcc4c4dc2ca11a8ea8fdb
I previously had separate inventories for each environment: prod, transport and
staging, with each inventory having a single xmpp_server group.
I want to start adopting group_vars so that I can share common variables
between hosts, so I've moved all hosts into a common hosts.yaml file with
groups for each environment.
This means there is no longer an xmpp_server group, and all hosts are in a
single inventory. Adjust the playbook to account for this.
Remove staging-fresh and prod-fresh targets2026-01-02T00:23:19ZMatthew Fennellmatthew@fennell.dev2026-01-02T00:23:19Zurn:sha1:51d48e2af6b4890fa9b58b5f2c036a6394f7e596
I initially created these targets so that I could easily redeploy a full server
from the terminal, including creating the necessary VPSs using my libcloud
helper repository.
However, a couple of years in, I have never done a -fresh deploy. While I am
planning to migrate to a different hosting provider soon, it doesn't have a
libcloud backend, so it turns out that this -fresh idea was overengineered and
unecessary.
I already have a runbook for transferring VPSs, so I can gradually automate
that instead if it becomes necessary.
Change license to AGPL-3.0-or-later2026-01-02T00:20:13ZMatthew Fennellmatthew@fennell.dev2026-01-02T00:20:13Zurn:sha1:66df8049eae4b3ec83467a81723b8b2d13f0b7ed
When I first made this playbook, I was a little sceptical of -or-later
licenses. However, I've come around to the idea over time.
Add transport make target2025-09-21T17:47:50ZMatthew Fennellmatthew@fennell.dev2025-09-21T17:47:50Zurn:sha1:9ea7d4d1634107de74427f9aaaaa4fd5f0b9b35a
This change allows targeted deployments just to transport servers, or
deployments to all prod servers (including transport) at once.
Use --diff flag in Makefile2025-07-05T22:17:33ZMatthew Fennellmatthew@fennell.dev2025-07-05T22:17:33Zurn:sha1:b20571406b685e5faf44b5d088db0376bc8ca0d5
This makes it easier to debug why a step is unexpectedly not idempotent.
Bring repo up-to-date with current prod config2024-04-04T21:54:05ZMatthew Fennellmatthew@fennell.dev2024-04-04T21:54:05Zurn:sha1:de867dadbcc3c69d97acf96bf3e86d11295eea39Add initial playbook2024-01-07T11:39:27ZMatthew Fennellmatthew@fennell.dev2024-01-07T11:39:27Zurn:sha1:8093a955e3c6238cc14537a54c56277af6b89dc2
At present, the playbook simply ensures that all required packages are
installed.