@psjbeisler I understand their position. The work and infrastructure required to build the packages we do (all 7 active Debian+Ubuntu versions across 4 architectures, for 2 branches of Prosody (stable and dev)) - it's a lot, and @zash does most of it.
In theory this is what distros are meant to take care of, but in practice they often lag behind (creating a support burden for us). It's also really nice to have our commits packaged automatically into nightly builds the next day.
Overall, worthwhile 🙂
distros "lagging behind" is exactly the problem I was trying to solve. Just including an extra automated Docker build would reduce the fragmentation and support issues w/ packages IMO
(Theres no ARM images for Prosody either actually 😟 )
Technically there are no Docker images for Prosody at all right now 🙂
When we switched to the new build system (to get ARM support) Docker builds stopped working for all architectures as they were based on the old system. We'll fix it, but we're juggling many other tasks as well, so I can't give an ETA.
As a Docker maximalist you can of course build the image yourself using the Dockerfile and Debian package 😉
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!