Darius Sagatauskas
Darius Sagatauskas
as I understand ejabberd uses standard Erlang logging output I would like to know if there is any solution ejbberd service `error` and `crash` logs send to elastic or journalctl...
### Summary Using a simple task to create ejabberd user ``` - name: Create xmpp user community.general.ejabberd_user: host: "test-xmpp.org" username: "bot-dev" password: "YZSdvce93FbeRopvT5s8vPVvP" ``` When I create ejabberd user always...
I tried this tool and it works perfectly, see that permissions only should be for `*` Resources ``` .... .... { "Sid": "VisualEditor1", "Effect": "Allow", "Action": "s3:ListAllMyBuckets", "Resource": "*" }...
Don't know if the module is suitable for latest nginx version but have compiled it for `nginx-1.25.3` Loaded module as well and tried to configure upstream and zone: ``` upstream...