Share

Application container customization

Warning:

Local installations of Flow Production Tracking are no longer offered. This documentation is intended only for those with existing instances of Shotgun Enterprise Docker. Click here for a list of our current offerings.

Note:

This article is intended for Flow Production Tracking System Administrators. It gives information about additional parameters that can be configured in for the shotgun-app container.

Environment variables

Different environment variables can be configured in the shotgun-app container. You may want to customize these values, based on the characteristics of your setup. Every time a variable is changed, the container needs to be restarted for the change to take effect.

Environment Variable Default value Description
MEMCACHED_HOST memcached Container or host name memcached
MEMCACHED_PORT 11211 OPTIONAL. Port on which memcached is listening to.
MEMCACHED_KEY_PREFIX <empty> OPTIONAL. The extra prefix that is added before the default Flow Production Tracking memcached prefix.

*Works in Shotgun v8.7.0.2979 and above and Flow Production Tracking.
PASSENGER_PROCESSES 12 OPTIONAL. The number of passenger processes handling requests. The ideal value corresponds to 1.5 times the number of processors on the host. Was MAX_PASSENGER_PROCESSES before 7.7.2.2
PASSENGER_MAX_REQUEST_QUEUE_SIZE 100 OPTIONAL. Passenger max queue size.
POSTGRES_DB shotgun OPTIONAL. Name of the Flow Production Tracking database
POSTGRES_HOST db OPTIONAL. Container or host name running the PostgreSQL server.
POSTGRES_PASSWORD <empty> OPTIONAL. Password to connect to the database using the POSTGRES_USER.
POSTGRES_PORT 5432 OPTIONAL. Port on which PostgreSQL is listening to.
POSTGRES_SCHEMA <empty> OPTIONAL. Name of the schema. Conventional Flow Production Tracking databases don’t use a schema.
POSTGRES_USER shotgun OPTIONAL. Name of the superadmin user that will be used for admin operations.
SHOTGUN_CUSTOM_CODE <empty> OPTIONAL. Name of the folder containing your custom code, minus _custom. Eg. If folder name is clientstudio_custom then the value would simply be clientstudio. Conventional Flow Production Tracking instances don’t use custom code. Was CUSTOM_CODE before 7.3.2.0.
SHOTGUN_ROLE <empty> OPTIONAL. The role of this Flow Production Tracking end-point. The end-point can be configured to respond only to API requests or only to UI requests. Accepted values are ui_server or api_server.
SHOTGUN_SITE_URL <empty> REQUIRED. The URL of the Flow Production Tracking end-point. The end-point can be different for application containers that are part of the same cluster. Should always be the URL of a server configured for ui_server role or a server without a defined SHOTGUN_ROLE (which provides ui_server by default) to ensure human users are redirected correctly.
SHOTGUN_ALT_URL <empty> OPTIONAL. The URL of an alternate Flow Production Tracking end-point. When configuring an application container explicitly for the ui_server role this value should be the URL of a server configured for the api_server role to ensure scripts are redirected correctly.
SHOTGUN_USER_ID 11000 OPTIONAL. Specifies the UID of the shotgun user inside the container which is used when writing files to the media storage.
SHOTGUN_USER_GID 11000 OPTIONAL. Specifies the GID of the shotgun user inside the container which is used when writing files to the media storage.

*Works in Shotgun v8.2.2.x and above and Flow Production Tracking.
SHOTGUN_LOG_LEVEL INFO OPTIONAL. Logging level for the shotgun application. Possible values: DEBUG, INFO, WARN, ERROR, FATAL.
IMAGEMAGICK_TIMEOUT 10s OPTIONAL. Duration allowed for small thumbnail generation before process is killed. Should be a floating point number with an optional suffix: 's' for seconds (the default), 'm' for minutes, 'h' for hours or 'd' for days. A duration of 0 removes the associated timeout.

Was this information helpful?