recipe-maintainers/mumble
0
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

[fix] Include default values in .env

Browse Source 
When a MUMBLE_CONFIG var is set, mumble will use it even if it is empty.
This caused problems e.g. when USERNAME="" caused all usernames to be
rejected.

One option to resolve this would be to keep unset-in-config variables
unset in the container. The other option is to supply mumble's default
values to the .env (which also makes the values more explicit).

This commit also removes a few config variables:
SSL would require more work to set up, as the server would need access
to the cert files
REGISTER is skipped for now as it would require an extra secret
LOG_DAYS is skipped because I'm not sure the logs are visible to the
user
This commit is contained in:
Amras
2026-04-27 14:45:29 +00:00
parent a96464676e
commit e8766522d2
2 changed files with 37 additions and 62 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
compose.yml
View File

@ -33,19 +33,7 @@ services:
MUMBLE_CONFIG_TEXTMESSAGELENGTH: ${TEXT_MESSAGE_LENGTH}
MUMBLE_CONFIG_IMAGEMESSAGELENGTH: ${IMAGE_MESSAGE_LENGTH}
MUMBLE_CONFIG_ALLOWHTML: ${ALLOW_HTML}
MUMBLE_CONFIG_LOGDAYS: ${LOG_DAYS}
MUMBLE_CONFIG_REGISTERNAME: ${REGISTER_NAME}
MUMBLE_CONFIG_REGISTERPASSWORD: ${REGISTER_PASSWORD}
MUMBLE_CONFIG_REGISTERURL: ${REGISTER_URL}
MUMBLE_CONFIG_REGISTERHOSTNAME: ${REGISTER_HOSTNAME}
MUMBLE_CONFIG_REGISTERLOCATION: ${REGISTER_LOCATION}
MUMBLE_CONFIG_BONJOUR: ${BONJOUR}
MUMBLE_CONFIG_SSLCERT: ${SSL_CERT}
MUMBLE_CONFIG_SSLKEY: ${SSL_KEY}
MUMBLE_CONFIG_SSLPASSPHRASE: ${SSL_PASSPHRASE}
MUMBLE_CONFIG_SSLCAPEM: ${SSL_CA_PEM}
MUMBLE_CONFIG_SSLDHPARAMS: ${SSL_DH_PARAMS}
MUMBLE_CONFIG_SSLCIPHERS: ${SSL_CIPHERS}
MUMBLE_CONFIG_OBFUSCATE: ${OBFUSCATE}
MUMBLE_CONFIG_CERTREQUIRED: ${CERT_REQUIRED}
MUMBLE_CONFIG_SENDVERSION: ${SEND_VERSION}