More XMPP updates
Dieser Commit ist enthalten in:
Ursprung
11bf5ccc4e
Commit
c54afa99ab
3 geänderte Dateien mit 40 neuen und 29 gelöschten Zeilen
|
@ -2,35 +2,6 @@ XMPP is provided by ejabberd, which describes itself as robust, scalable and ext
|
||||||
|
|
||||||
So first of all, thanks to ejabberd and its contributers!
|
So first of all, thanks to ejabberd and its contributers!
|
||||||
|
|
||||||
## FAQs
|
|
||||||
|
|
||||||
- **Are messages stored on the server?**
|
|
||||||
|
|
||||||
Not by default. The default setting is to disable the message archive via mod_mam but allow users to enable the function if they want to:
|
|
||||||
|
|
||||||
```
|
|
||||||
mod_mam:
|
|
||||||
clear_archive_on_room_destroy: true
|
|
||||||
default: never
|
|
||||||
compress_xml: true
|
|
||||||
request_activates_archiving: true
|
|
||||||
```
|
|
||||||
|
|
||||||
- **Are uploaded files stored on the server?**
|
|
||||||
|
|
||||||
Yes, uploaded files are stored in the volume `xmpp-uploads-vol-1`.
|
|
||||||
|
|
||||||
The retention policy saves them for 30 days:
|
|
||||||
|
|
||||||
```
|
|
||||||
mod_http_upload_quota:
|
|
||||||
max_days: 30
|
|
||||||
```
|
|
||||||
|
|
||||||
- **Are messages stored when a JID is offline?**
|
|
||||||
|
|
||||||
Yes, up to 1000 messages are stored.
|
|
||||||
|
|
||||||
## Enable XMPP in mailcow
|
## Enable XMPP in mailcow
|
||||||
|
|
||||||
To enable XMPP for a domain, you need to edit the given domain in mailcow UI:
|
To enable XMPP for a domain, you need to edit the given domain in mailcow UI:
|
||||||
|
|
38
docs/u_e-xmpp-faq.md
Normale Datei
38
docs/u_e-xmpp-faq.md
Normale Datei
|
@ -0,0 +1,38 @@
|
||||||
|
## FAQ
|
||||||
|
|
||||||
|
- **I do not want to run ejabberd, is there a `SKIP_XMPP` variable?**
|
||||||
|
|
||||||
|
No, there is not. But you don't need one either.
|
||||||
|
|
||||||
|
The xmppd behaves the same way as SOGo or Solr do when disabled. A shell will be idling and ejabberd will **not** be started.
|
||||||
|
|
||||||
|
As soon as a domain is enabled for XMPP, the container will be restarted and ejabberd bootstrapped.
|
||||||
|
|
||||||
|
ejabberd is **very** light on resources, you may want to give it a try.
|
||||||
|
|
||||||
|
- **Are messages stored on the server?**
|
||||||
|
|
||||||
|
Not by default. The default setting is to disable the message archive via mod_mam but allow users to enable the function if they want to:
|
||||||
|
|
||||||
|
```
|
||||||
|
mod_mam:
|
||||||
|
clear_archive_on_room_destroy: true
|
||||||
|
default: never
|
||||||
|
compress_xml: true
|
||||||
|
request_activates_archiving: true
|
||||||
|
```
|
||||||
|
|
||||||
|
- **Are uploaded files stored on the server?**
|
||||||
|
|
||||||
|
Yes, uploaded files are stored in the volume `xmpp-uploads-vol-1`.
|
||||||
|
|
||||||
|
The retention policy saves them for 30 days:
|
||||||
|
|
||||||
|
```
|
||||||
|
mod_http_upload_quota:
|
||||||
|
max_days: 30
|
||||||
|
```
|
||||||
|
|
||||||
|
- **Are messages stored when a JID is offline?**
|
||||||
|
|
||||||
|
Yes, up to 1000 messages are stored.
|
|
@ -97,6 +97,8 @@ nav:
|
||||||
- 'Rspamd': 'u_e-rspamd.md'
|
- 'Rspamd': 'u_e-rspamd.md'
|
||||||
- 'SOGo': 'u_e-sogo.md'
|
- 'SOGo': 'u_e-sogo.md'
|
||||||
- 'XMPP': 'u_e-xmpp-enable.md'
|
- 'XMPP': 'u_e-xmpp-enable.md'
|
||||||
|
- 'FAQ': 'u_e-xmpp-faq.md'
|
||||||
|
- 'Enable XMPP': 'u_e-xmpp-enable.md'
|
||||||
- 'Docker':
|
- 'Docker':
|
||||||
- 'Customize Dockerfiles': 'u_e-docker-cust_dockerfiles.md'
|
- 'Customize Dockerfiles': 'u_e-docker-cust_dockerfiles.md'
|
||||||
- 'Docker Compose Bash Completion': 'u_e-docker-dc_bash_compl.md'
|
- 'Docker Compose Bash Completion': 'u_e-docker-dc_bash_compl.md'
|
||||||
|
|
Laden …
In neuem Issue referenzieren