sample-development.engine.ini

##############################################
#            Engine Configuration            #
##############################################

[general]
# Path to the engine-core socket directory relative to the engine project root
socket_dir="../engine-core/socket"
# Directory where the log file resides
log_dir="logs"
# Possible values: debug, info, warning, error, critical
log_level="info"

[monitoring]
# Mail server credentials for sending email notifications (Admin and Programme Coordination)
mail_server="mail.your-radio.org"
mail_server_port="587"
mail_user="aura@subsquare.at"
mail_pass="---SECRET--PASSWORD---"
# Set to "true" if you want to notify programme-coordinators about about fallback situations, otherwise "false"
mail_coordinator_enabled="false"
# If you want to address multiple programme-coordinators separate their emails by space
coordinator_mail="programme-coordinator@your-radio.org"
# Set to "true" if you want to notify admins about incidents, otherwise "false"
mail_admin_enabled="false"
# If you want to address multiple administrators separate their emails by space
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]"

# Server where heartbeat info is sent to
heartbeat_server = "127.0.0.1"   
# Some UDP port
heartbeat_port = 43334 
# Seconds how often the vitality of the Engine should be checked (0 = disabled)
heartbeat_frequency = 0

[api]
## STEERING ##
# The URL to get the health status 
api_steering_status="http://localhost:8000/api/v1/"
# The URL to get the Calendar via Steering
api_steering_calendar="http://localhost:8000/api/v1/playout"

## TANK ##
# The session name which is used to authenticate against Tank
api_tank_session="engine"
# The secret which is used to authenticate against Tank
api_tank_secret="rather-secret"
# The URL to get the health status 
api_tank_status="http://localhost:8040/healthz/"
# The URL to get playlist details via Tank
api_tank_playlist="http://localhost:8040/api/v1/playlists/${ID}"

## ENGINE-API ##
# Engine ID (1 or 2)
api_engine_number=1
# Engine API availability check
api_engine_status="http://localhost:8008/api/v1/ui/"
# Engine API endpoint to store playlogs
api_engine_store_playlog="http://localhost:8008/api/v1/playlog"
# Engine API endpoint to store clock information
api_engine_store_clock="http://localhost:8008/api/v1/clock"
# Engine API endpoint to store health information
api_engine_store_health="http://localhost:8008/api/v1/source/health/${ENGINE_NUMBER}"

[scheduler]
# 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="../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="../audio/playlist"
# Offset in seconds how long it takes for Liquidsoap to actually execute a scheduler command; Crucial to keep things in sync
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 aired
fetching_frequency=30
# The schedule is fetched on every "fetching_frequency" cycle and stored in a local database
db_user="aura"
db_name="aura_engine"
db_pass="---SECRET--PASSWORD---"
db_host="localhost"
db_charset="utf8"
# 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=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=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=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="1.5"
fade_out_time="1.5"