a2ac9c45f0
I considered adding IPv6 support to the OCSP responder but it would add more files and complexity for (I think) little gain. Instead this change keeps the OCSP responder on IPv4 only, but makes sure it's properly configured in the hosts file even when using the -6 flag. The OCSP responder will always use IPv4, other services will be able to reach it via IPv4 regardless of whether they're using IPv6 for their own communication. |
||
|---|---|---|
| _common | ||
| cluster | ||
| cluster_with_federation | ||
| federation | ||
| proxy | ||
| scripts | ||
| simple | ||
| .gitignore | ||
| README.md | ||
| stop.sh | ||
README.md
Multiple Openfires in Docker
Quickly create multiple Openfire servers with associated PostgreSQL DBs in Docker containers for local testing.
Data and config snapshots have been taken of each DB and Openfire server so that a known desired state is configured on start. See the "How it's built" section below if you want to understand how this was done or need to add more nodes.
Prerequisites
-
Docker Compose - https://docs.docker.com/compose/install/
docker build -t openfire:latest .
Quick Start
- Make sure you have docker and docker-compose installed
- Create a local Openfire docker image, tagged
openfire:latestthat contains the version of Openfire that you want to run- run
docker build --tag openfire:latest .in the root of the Openfire repository (https://github.com/igniterealtime/Openfire)
- run
- Launch the environment using the
start.shin the directory of your choice.
How it's built
To recreate the known good state for the system we first create base Openfire and relevant database containers. We then perform the manual setup and any other configuration that we require, such as adding users and MUC rooms. Once the setup is complete we dump the database from the container to the Docker host and copy the Openfire config files from the container to the Docker host. These are then used with Docker volumes for creating the same state in subsequent Openfire and database containers.