shotgunEventDaemon.conf

[daemon]
# General daemon operational settings

# The pidFile is the location where the daemon will store its process id. If
# this file is removed while the daemon is running, it will shutdown cleanly
# after the next pass through the event processing loop.
pidFile: /var/log/shotgunEventDaemon/shotgunEventDaemon.pid

# The eventIdFile is the location where the daemon will store the id of the last
# processed event. This will allow the daemon to pick up where it left off when
# last shutdown thus not missing any events. If you want to ignore any events
# since last daemon shutdown, remove this file before daemon startup and the
# daemon will process only new events created after startup.
eventIdFile: /var/log/shotgunEventDaemon/shotgunEventDaemon.id

# The logging mode to operate in:
# 0 = all log message in the main log file
# 1 = one main file for the engine, one file per plugin
logMode: 1

# The path where to put log files
logPath: /var/log/shotgunEventDaemon

# The name of the daemon log file. The setup is for 10 log files that rotate
# every night at midnight
logFile: shotgunEventDaemon

# The level of logging that should be sent to the log file. This value is only
# applicable to for the main dispatching engine and can be overriden on a per
# plugin basis. This value is passed to the logging library. Any positive
# integer value is valid but most common cases are:
# - 10 - Debug
# - 20 - Info
# - 30 - Warnings
# - 40 - Error
# - 50 - Critical
logging: 20

# Enable Timing logging
# Timing logging is a separate log file that will log timing information regarding
# event dispatching and processing run time. This is to help diagnose which plugins
# are taking the most amount of time and where any potential queue processing
# delay might be coming from. Valid values are `on` or to enable or anything else
# to disable.
# timing_log: on
timing_log: off

# If the connection to shotgun fails, number of seconds to wait until we retry.
# This allows for occasional network hiccups, server restarts, application maintenance,
# etc.
conn_retry_sleep = 60

# Number of times to retry connection before logging an error level message (which
# sends an email in the default configuration)
max_conn_retries = 5

# Number of seconds to wait before requesting new events after each batch of events
# is done processing
fetch_interval = 5

# Maimum number of events to fetch at once.
max_event_batch_size = 500


[shotgun]
# Shotgun connection options for the daemon

# The Shotgun url the event processing framework should connect to.
server: %(SG_ED_SITE_URL)s

# The Shotgun script name the framework should connect with.
name: %(SG_ED_SCRIPT_NAME)s

# The Shotgun api key the framework should connect with. You'll need to replace
# this random useless key with the one corresponding to the script you've setup.
key: %(SG_ED_API_KEY)s

# The address of the proxy server used to connect to your Shotgun server
# in the format 111.222.333.444:8080. Leave this empty if you don't have
# a proxy server.
proxy_server:

# Sets the session_uuid from every event in the Shotgun instance to propagate in
# any events generated by plugins. This will allow the Shotgun UI to display
# updates that occur as a result of a plugin.
#
# Shotgun server v2.3+ required.
# Shotgun API v3.0.5+ required
use_session_uuid: True


[plugins]
# Plugin related settings

# A comma delimited list of paths where the framework should look for plugins to
# load.
paths: /app/sgEventsPlugins


[emails]
# Email notification settings. These are used for error reporting because we
# figured you wouldn't constantly be tailing the log and would rather have an
# active notification system.
#
# Any error above level 40 (ERROR) will be reported via email.
#
# All of these value must be provided for there to be email alerts sent out.

# The server that should be used for smtp connections. The username and password
# values can be uncommented to supply credentials for the smtp connection. The
# smtp port can also be uncommented to supply an alternate port such as 587 for
# GMail TLS SMTP. As for the useTLS parameter, it is a True/False value.
server: smtp.yourdomain.com
#port: 587
#useTLS: True
#username: %(SG_ED_EMAIL_USERNAME)s
#password: %(SG_ED_EMAIL_PASSWORD)s

# The from address that should be used in emails.
from: support@yourdomain.com

# A comma delimited list of email addresses to whom these alerts should be sent.
to: you@yourdomain.com

# An email subject prefix that can be used by mail clients to help sort out
# alerts sent by the Shotgun event framework.
subject: [SG]