Skip to content
Snippets Groups Projects
Commit 775e3065 authored by David Trattnig's avatar David Trattnig
Browse files

Fix(config): Expose only mandatory as env #113

parent 5fd5f3b8
No related branches found
No related tags found
No related merge requests found
Pipeline #2196 passed
......@@ -8,36 +8,36 @@ socket_dir="/srv/socket"
# Directory where the log file resides
log_dir="logs"
# Possible values: debug, info, warning, error, critical
log_level="${ENGINE_LOG_LEVEL}"
log_level="info"
# Details for the Station Fallback
fallback_show_name="${ENGINE_FALLBACK_SHOW_NAME}"
fallback_show_id="${ENGINE_FALLBACK_SHOW_ID}"
fallback_show_name="Random Music"
fallback_show_id="-1"
[monitoring]
# Mail server credentials for sending email notifications (Admin and Programme Coordination)
mail_server="${ENGINE_MONITORING_MAIL_SERVER}"
mail_server_port="${ENGINE_MONITORING_MAIL_SERVER_PORT}"
mail_user="${ENGINE_MONITORING_MAIL_USER}"
mail_pass="${ENGINE_MONITORING_MAIL_PASSWORD}"
mail_server="mail.aura.radio"
mail_server_port="587"
mail_user="userid_mailbox"
mail_pass="---SECRET--PASSWORD---"
# Set to "true" if you want to notify programme-coordinators about about fallback situations, otherwise "false"
mail_coordinator_enabled="${ENGINE_MONITORING_MAIL_COORDINATOR_ENABLED}"
mail_coordinator_enabled="false"
# If you want to address multiple programme-coordinators separate their emails by space
coordinator_mail="${ENGINE_MONITORING_COORDINATOR_MAIL}"
coordinator_mail="programme-coordinator@aura.radio"
# Set to "true" if you want to notify admins about incidents, otherwise "false"
mail_admin_enabled="${ENGINE_MONITORING_ADMIN_MAIL_ENABLED}"
mail_admin_enabled="false"
# If you want to address multiple administrators separate their emails by space
admin_mail="${ENGINE_MONITORING_ADMIN_MAIL}"
admin_mail="admin@aura.radio"
# The FROM email address used when sending
from_mail="${ENGINE_MONITORING_SENDER_MAILADDRESS}"
from_mail="monitoring@aura.radio"
# A subject prefix allows applying filter rules in your mail client
mailsubject_prefix="${ENGINE_MONITORING_MAIL_SUBJECT_PREFIX}" # default: [AURA Engine]
mailsubject_prefix="[AURA Engine]" # default: [AURA Engine]
# Seconds how often the vitality of Engine Core should be checked (default=1)
heartbeat_frequency=${ENGINE_HEARTBEAT_FREQUENCY}
heartbeat_frequency=1
# Host where heartbeat is sent to (disabled if empty string)
heartbeat_server="${ENGINE_HEARTBEAT_SERVER}"
heartbeat_server=""
# Some UDP port
heartbeat_port=${ENGINE_HEARTBEAT_SERVER_PORT}
heartbeat_port=43334
[api]
## STEERING ##
......@@ -77,29 +77,29 @@ db_pass="${ENGINE_DB_PASS}"
db_host="${ENGINE_DB_HOST}"
db_charset="utf8"
# Base path as seen by "engine-core", not accessed by "engine"; this is required to construct the absolute audio file path (check "Audio Store" in the docs)
# Either provide an absolute base path or a relative one starting in the `engine-core/src` directory. In case of `engine-core` running in docker use `/var/audio/source`
audio_source_folder="${ENGINE_AUDIO_SOURCE_FOLDER}"
audio_source_extension="${ENGINE_AUDIO_SOURCE_EXTENSION}"
# Either provide an absolute base path or a relative one starting in the `engine` directory. In case of `engine-core` running in docker use `/var/audio/source`
audio_source_folder="../engine-core/audio/source"
audio_source_extension=".flac"
# Folder holding M3U Playlists to be scheduled in form of Engine Playlists (similar as audio source folder above)
audio_playlist_folder="${ENGINE_AUDIO_PLAYLIST_FOLDER}"
# Offset in seconds how long it takes for Liquidsoap to actually execute a scheduler command; Crucial to keep things in sync
engine_latency_offset=${ENGINE_LATENCY_OFFSET}
engine_latency_offset=0.5
# How often should the calendar be fetched in seconds. This determines the time of the last changes applied, before a specific show is aired
fetching_frequency=${ENGINE_FETCHING_FREQUENCY}
fetching_frequency=30
# The scheduling window defines when the entries of each timeslot are queued for play-out. The windows start at (timeslot.start - window_start) seconds
# and ends at (timeslot.end - window.end) seconds. Its also worth noting, that timeslots can only be deleted before the start of the window.
scheduling_window_start=${ENGINE_SCHEDULING_WINDOW_START}
scheduling_window_end=${ENGINE_SCHEDULING_WINDOW_END}
scheduling_window_start=60
scheduling_window_end=60
# How many seconds before the actual schedule time the entry should be pre-rolled. Note to provide enough timeout for
# contents which take longer to load (big files, bad connectivity to streams etc.). If the planned start time is in
# the past the offset is ignored and the entry is played as soon as possible
preload_offset=${ENGINE_PRELOAD_OFFSET}
preload_offset=15
# Sometimes it might take longer to get a stream connected. Here you can define a viable length.
# But note, that this may affect the preloading time (see `preload_offset`), hence affecting the
# overall playout, it's delays and possible fallbacks
input_stream_retry_delay=${ENGINE_INPUT_STREAM_RETRY_DELAY}
input_stream_max_retries=${ENGINE_INPUT_STREAM_MAX_RETRIES}
input_stream_buffer=${ENGINE_INPUT_STREAM_BUFFER}
# overall playout, its delays and possible fallbacks
input_stream_retry_delay=1
input_stream_max_retries=10
input_stream_buffer=3.0
# How long we have to fade in and out, when we select another mixer input (seconds))
fade_in_time="${ENGINE_FADE_IN_TIME}"
fade_out_time="${ENGINE_FADE_OUT_TIME}"
fade_in_time="1.5"
fade_out_time="1.5"
......@@ -30,7 +30,7 @@ admin_mail="david@subsquare.at"
# The FROM email address used when sending
from_mail="monitoring@aura.engine"
# A subject prefix allows applying filter rules in your mail client
mailsubject_prefix="[AURA Engine]"
mailsubject_prefix="[AURA Engine]" # default: [AURA Engine]
# Seconds how often the vitality of Engine Core should be checked (default=1)
heartbeat_frequency=1
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment