summaryrefslogtreecommitdiff
path: root/files/prosody.cfg.lua.j2
diff options
context:
space:
mode:
authorMatthew Fennell <matthew@fennell.dev>2026-01-02 00:23:19 +0000
committerMatthew Fennell <matthew@fennell.dev>2026-01-02 00:23:19 +0000
commit51d48e2af6b4890fa9b58b5f2c036a6394f7e596 (patch)
tree1dadf18920f41e209a9629b7de089a53702d6d1b /files/prosody.cfg.lua.j2
parent66df8049eae4b3ec83467a81723b8b2d13f0b7ed (diff)
Remove staging-fresh and prod-fresh targets
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.
Diffstat (limited to 'files/prosody.cfg.lua.j2')
0 files changed, 0 insertions, 0 deletions