Apply the change from
|
||
|---|---|---|
| .. | ||
| plugins | ||
| sql | ||
| xmpp/conf | ||
| README.md | ||
| docker-compose-network-dualstack.yml | ||
| docker-compose-network-ipv4-only.yml | ||
| docker-compose.yml | ||
| start.sh | ||
README.md
Simple configuration
Running ./start.sh will perform some cleanup then start the containers in a simple configuration.
When running, the system looks like this:
+--------------------------+
| |
| 172.60.0.10 |
| +--------+ |
(XMPP-C2S) 5222 -| | | |
(XMPP-S2S) 5269 -|------| XMPP 1 + |
(HTTP-Admin) 9090 -| | | |
(BOSH) 7070 -| +----+---+ |
| | |
| | |
| +---+--+ |
| | | |
(Database) 5432 -|-------| DB + |
| | | |
| +------+ |
| 172.60.0.11 |
| |
+-----172.60.0.0/24--------+
Openfire is configured with the following XMPP domain:
xmpp.localhost.example
Openfire is configured with the following FQDN:
xmpp1.localhost.example
The following users are configured:
adminadminuser1passworduser2password
The following MUC rooms are configured:
muc1muc2
Network
The Docker compose file defines a custom bridge network with a single subnet of 172.60.0.0/24.
When the -6 argument to ./start.sh is provided, then an additional subnet of fd23:0d79:d076::/64 is configured.
Then, IPv6 is preferred for internal networking. Note that the IPv4 network remains in place, as Docker does not support
IPv6-only containers.
When running with the optional -6 flag (that adds IPv6 support) the system looks like this:
+--------------------------+
| |
| [fd23:d79:d076::10] |
| 172.60.0.10 |
| +--------+ |
(XMPP-C2S) 5222 -| | | |
(XMPP-S2S) 5269 -|------| XMPP 1 + |
(HTTP-Admin) 9090 -| | | |
(BOSH) 7070 -| +----+---+ |
| | |
| | |
| +---+--+ |
| | | |
(Database) 5432 -|-------| DB + |
| | | |
| +------+ |
| 172.60.0.11 |
| [fd23:d79:d076::11] |
| |
+-----172.60.0.0/24--------+
fd23:0d79:d076::/64