Skip to content

v1.4.2 - Reload Config Variables
Compare
Choose a tag to compare
@Askaholic Askaholic released this 04 May 23:51
· 225 commits to develop since this release
v1.4.2
6ec63d4
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Summary

Config variables are loaded from a file instead of environment variables. This means they can be reloaded without restarting the server.

Deployment Notes

  1. Set environment variable CONFIGURATION_FILE to the config file path.
  2. Create a config file (yaml) to override needed config settings (keys not present in the file will use the default values).
  3. Mount the file as a docker volume so that CONFIGURATION_FILE points to the file path inside the container.

Example:

USE_API: true
LOG_LEVEL: "INFO"
COTURN_HOSTS: ["host1.example.com", "host2.example.com"]

There is also another example in tests/data/test_conf.yaml

When config variables are reloaded any changes will be logged at the info level. This can be used to verify that everything is set up correctly, but note that by default CONFIGURATION_REFRESH_TIME is set to 300 seconds.

Pull Requests

  • Reload Configuration Variables (#570) [by UmbraSolis]
  • Bump faf-stack version to v20.4.18 (#578) [by UmbraSolis]
Assets 2
Loading