Closed fredericmoulins closed 1 year ago
I rebased this branch on dev
(and forced-pushed). Git followed the directory moves without issue.
I have notes about trying to keep the certificates in the letsencrypt directory and probably use cert-perms
. I might try to do that also on this branch, or later.
I agree with the move for bullseye.
These changes address the warnings seen in the logs of ejabberd on buster, and should help for any more recent version. It should be tested on bullseye (especially the mod_bosh, if it's needed).
I have ejabberd working in the bullseye branch. I am now deploying the system from scratch, to see what is working and what is not.
I think we can close this PR, as I have now ejabberd working on Bullseye. @fredericmoulins, have a look and tell me.
Implemented
Some changes needed in the ejabberd configuration for buster, and some others to address deprecation warnings.
Those changes are for the ejabberd version in buster, it will break a configuration for the stretch version.