Skip to content
Permalink
main
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

docker/comanage-match/docs/volumes-and-data-persistence.md

Go to file
 
 
Cannot retrieve contributors at this time
66 lines (49 sloc) 2.36 KB
Raw Blame
Open in GitHub Desktop

COmanage Match Volumes and Data Persistence

COmanage Match requires a relational database. See other documentation in this repository for examples of how to orchestrate a COmanage Match container together with an container providing a relational database service, and for details on how to configure the COmanage Match container to connect to the database.

Additionally COmanage Match requires a persistent directory into which a few files and a specific directory structure needed by COmanage Match will be written.

The persistent directory must be provided either using a Docker volume or a bind mount.

The directory path inside the container that must be mounted is /src/comanage-match/local.

For example to use a bind mount from the local Docker engine host:

sudo mkdir -p /opt/comanage-match-local

and then when instantiating the container

docker run -d \
  --name comanage-match \
  -v /opt/comanage-match-local:/srv/comanage-match/local \
  -p 80:80 \
  -p 443:443 \
  comanage-match:1.0.0-shibboleth-sp-1

After the image is instantiated into a container for the first time the entrypoint script will create the necessary directory structure along with the database.php and other necessary files using database and other details found in environment variables.

After the first instantiation of the container later restarts will not overwrite database configuration or any other details in the persistent directory, even if the values for the environment variables change.