Rewrite the certificate section to more precisely describe both alternatives in a more concise manner. Additionally, remove the references to Let's Encrypt as the certificate's origin is irrelevant.
1.4 KiB
Docker Compose
Configuring Murmur
-
Create a new directory and switch to it
-
Create the file
docker-compose.ymland copy the default docker-compose.yml into it -
Create the directory
dataand make1000its owner -
Create the file
murmur.iniand copy the default murmur.ini into it -
Change
databaseinmurmur.inito/var/lib/murmur/murmur.sqlite -
Run
docker-compose up -d
Viewing the log
Run docker logs mumble-server.
Using the release build instead of the master branch
Change #master at the end of the build line in docker-compose.yml to the branch you want to compile. For example, build: github.com/mumble-voip/mumble#1.4.x will build version 1.4.x.
Adding a certificate
First, give Murmur permission to read the certificate files. There are two options for this:
- Move the certificate files to a location user
1000can read - Have Murmur read the certificate files as
rootand then switch accounts. This is done by addinguser: "0:0"todocker-compose.ymland changingunametouname=murmurinmurmur.ini
Then add a volume with the certificate files in the volume section of docker-compose.yml: - /path/to/certificate-directory/:/certs:ro.
Finally, change sslCert and sslKey in murmur.ini to their respective paths and run docker-compose down followed by docker-compose up -d.