Environment Variables

Each service has a list of environment variables which define its configuration for runtime. Use this reference to understand what each environment variable does, what it is used for and the possible values it can contain.

ThrillPots Gateway

Variable NameDefault ValueDescription
GW_LOG_LEVELinfoThe log level at which logs will be written. Possible values are info, debug, warn, trace
GW_WEB_HOST0.0.0.0The hostname to bind the web service to
GW_WEB_PORT80The port to bind the web service to
GW_MONGO_HOSTmongodb://localhostThe connection URI for the MongoDB server
GW_MONGO_DB_NAMEtestThe DB name for the Service (should usually be set to thrillpots-gateway)
GW_MONGO_USERNAMENone[Optional] The username to use to authenticate with MongoDB
GW_MONGO_PASSWORDNone[Optional] The password to use to authenticate with MongoDB
GW_MONGO_RETRY_WRITEStrueFlag to set whether writes are retries when they fail
GW_REDIS_HOSTredis://localhostThe connection URI for REDIS. Possible schemas are:

- Standalone: redis://hostname:port

- Cluster: redis://hostname:port,redis://hostname2:port,..

- Sentinel: sentinel://hostname:port/master/replica or sentinel+tls://hostname:port/master/replica
GW_REDIS_DB0The Redis DB number to use
GW_REDIS_USERNAMENone[Optional] The REDIS username to use for authentication
GW_REDIS_PASSWORDNone[Optional] The REDIS password to use for authentication
GW_REDIS_SECUREfalse[Optional] Defines if the REDIS connection is secure or not
GW_REDIS_CLUSTERfalse[Optional] Defines if the REDIS connection is secure or not. For a standard Sentinel deployment, this variable should be set to false
GW_JPSERVER_HOSThttp://localhost:8084The URL for the ThrillPots Service. For clustered environments, this should point to the DNS entry for the ThrillPots Service on your internal load balancer
GW_THRILLID_HOSThttp://localhost:9000The URL for the Thrill-ID Service. For clustered environments, this should point to the DNS entry for the Thrill-ID Service on your internal load balancer
GW_THRILLID_USERNAMENoneThe username the service should use to authenticate with Thrill-ID. In a standard deployment, this should be set to thrillpots.gateway
GW_THRILLID_PASSWORDNoneThe password the service should use to authenticate with Thrill-ID. In a default deployment, this will start off as password and can be changed via Thrill-ID directly
GW_THRILLGATE_HOSTNoneThe URL for the ThrillGate Service. For clustered environments, this should point to the DNS entery for the ThrillGate Service on your internal load balancer

Back to Top

ThrillPots Service

Variable NameDefault ValueDescription
JP_LOG_LEVELinfoThe log level at which logs will be written. Possible values are info, debug, warn, trace
JP_WEB_HOST0.0.0.0The hostname to bind the web service to
JP_WEB_PORT80The port to bind the web service to
JP_MONGO_HOSTmongodb://localhostThe connection URI for the MongoDB server
JP_MONGO_DB_NAMEthrillpotsThe DB name for the Service (should usually be set to thrillpots)
JP_MONGO_USERNAMENone[Optional] The username to use to authenticate with MongoDB
JP_MONGO_PASSWORDNone[Optional] The password to use to authenticate with MongoDB
JP_MONGO_RETRY_WRITEStrueFlag to set whether writes are retries when they fail
JP_REDIS_HOSTredis://localhostThe connection URI for REDIS. Possible schemas are:

- Standalone: redis://hostname:port

- Cluster: redis://hostname:port,redis://hostname2:port,..

- Sentinel: sentinel://hostname:port/master/replica or sentinel+tls://hostname:port/master/replica
JP_REDIS_DB0The Redis DB number to use
JP_REDIS_USERNAMENone[Optional] The REDIS username to use for authentication
JP_REDIS_PASSWORDNone[Optional] The REDIS password to use for authentication
JP_REDIS_SECUREfalse[Optional] Defines if the REDIS connection is secure or not
JP_REDIS_CLUSTERfalse[Optional] Defines if the REDIS connection is secure or not. For a standard Sentinel deployment, this variable should be set to false
JP_THRILLID_HOSThttp://localhost:9000The URL for the Thrill-ID Service. For clustered environments, this should point to the DNS entry for the Thrill-ID Service on your internal load balancer
JP_THRILLID_USERNAMEthrillpotsThe username the service should use to authenticate with Thrill-ID. In a standard deployment, this should be set to thrillpots
JP_THRILLID_PASSWORDpasswordThe password the service should use to authenticate with Thrill-ID. In a default deployment, this will start off as password and can be changed via Thrill-ID directly
JP_SERVICE_CURRENCY_REFRESH86400000The amount of time between ThrillPots attempting to refresh its currency multipliers. The default is set to 24 hours (86400000 milliseconds)
JP_SERVICE_UPDATE_EVENT_FREQUENCY10000The amount of time (in milliseconds) between jackpot update events being sent out. The default is set to 10 seconds, but we recommend reducing this to a value between 2000 and 5000 (2s - 5s)
JP_SERVICE_AUTH_CACHE_TTL300The number of seconds to cache a player's authentication token. Change this to reflect the TTL on your system's player session token lifetimes
JP_RNG_BACKGROUND_CYCLINGfalseIf set to true, the RNG will automatically perform background cycling of its values in periods defined by JP_RNG_BACKGROUND_CYCL_DELAY_MIN_SECS and JP_RNG_BACKGROUND_CYCLE_DELAY_MAX_SECS
JP_RNG_BACKGROUND_CYCLE_DELAY_MIN_SECS0[Optional] The minimum amount of delay between background cycles. We recommend a value of 60
JP_RNG_BACKGROUND_CYCLE_DELAY_MAX_SECS0[Optional] The maximum amount of delay between background cycles. We recommend a value of 180
JP_RNG_MONITOR_PERIOD_SECS0[Optional] The maximum period between the randomness monitoring test running. We recommend a value of 600
JP_RNG_FAILURES_TO_ALERTNone[Optional] If RNG Monitoring is enabled, this variable defines the number of consecutive failures that are needed to generate an alert. We recommend setting this to a value of 5 or higher
JP_CC_URLNoneThe URL of the ThrillTech CC Service which must be defined for all operator environments. For STAGING environments, this value should be set to https://cc-stg.thrillpots.io and for PRODUCTION environments, it should be set to: https://cc.thrilltechapi.com
JP_CC_OPERATOR_IDNoneThis value identifies you as an operator and will be provided to you by ThrillTech
JP_CC_SERVICE_IDNoneThis identifies the product and should be set to thrillpots

Back to Top

ThrillGate Service

Variable NameDefault ValueDescription
TG_LOG_LEVELinfoThe log level at which logs will be written. Possible values are info, debug, warn, trace
TG_WEB_HOST0.0.0.0The hostname to bind the web service to
TG_WEB_PORT80The port to bind the web service to
TG_MONGO_HOSTmongodb://localhostThe connection URI for the MongoDB server
TG_MONGO_DB_NAMEtestThe DB name for the Service (should usually be set to thrillgate)
TG_MONGO_USERNAMENone[Optional] The username to use to authenticate with MongoDB
TG_MONGO_PASSWORDNone[Optional] The password to use to authenticate with MongoDB
TG_MONGO_RETRY_WRITEStrueFlag to set whether writes are retries when they fail
TG_REDIS_HOSTredis://localhostThe connection URI for REDIS. Possible schemas are:

- Standalone: redis://hostname:port

- Cluster: redis://hostname:port,redis://hostname2:port,..

- Sentinel: sentinel://hostname:port/master/replica or sentinel+tls://hostname:port/master/replica
TG_REDIS_DB0The Redis DB number to use
TG_REDIS_USERNAMENone[Optional] The REDIS username to use for authentication
TG_REDIS_PASSWORDNone[Optional] The REDIS password to use for authentication
TG_REDIS_SECUREfalse[Optional] Defines if the REDIS connection is secure or not
TG_REDIS_CLUSTERfalse[Optional] Defines if the REDIS connection is secure or not. For a standard Sentinel deployment, this variable should be set to false
TG_THRILLID_HOSThttp://localhost:9000The URL for the Thrill-ID Service. For clustered environments, this should point to the DNS entry for the Thrill-ID Service on your internal load balancer
TG_THRILLID_USERNAMENoneThe username the service should use to authenticate with Thrill-ID. In a standard deployment, this should be set to thrillgate
TG_THRILLID_PASSWORDNoneThe password the service should use to authenticate with Thrill-ID. In a default deployment, this will start off as password and can be changed via Thrill-ID directly

Back to Top

ThrillConnect Service

Variable NameDefault ValueDescription
TCS_LOG_LEVELinfoThe log level at which logs will be written. Possible values are info, debug, warn, trace
TCS_WEB_HOST0.0.0.0The hostname to bind the web service to
TCS_WEB_PORT80The port to bind the web service to
TCS_MONGO_HOSTmongodb://localhostThe connection URI for the MongoDB server
TCS_MONGO_DB_NAMEtestThe DB name for the Service (should usually be set to thrillconnect)
TCS_MONGO_USERNAMENone[Optional] The username to use to authenticate with MongoDB
TCS_MONGO_PASSWORDNone[Optional] The password to use to authenticate with MongoDB
TCS_MONGO_RETRY_WRITEStrueFlag to set whether writes are retries when they fail
TCS_REDIS_HOSTredis://localhostThe connection URI for REDIS. Possible schemas are:

- Standalone: redis://hostname:port

- Cluster: redis://hostname:port,redis://hostname2:port,..

- Sentinel: sentinel://hostname:port/master/replica or sentinel+tls://hostname:port/master/replica
TCS_REDIS_DB0The Redis DB number to use
TCS_REDIS_USERNAMENone[Optional] The REDIS username to use for authentication
TCS_REDIS_PASSWORDNone[Optional] The REDIS password to use for authentication
TCS_REDIS_SECUREfalse[Optional] Defines if the REDIS connection is secure or not
TCS_REDIS_CLUSTERfalse[Optional] Defines if the REDIS connection is secure or not. For a standard Sentinel deployment, this variable should be set to false
TCS_THRILLID_HOSThttp://localhost:9000The URL for the Thrill-ID Service. For clustered environments, this should point to the DNS entry for the Thrill-ID Service on your internal load balancer
TCS_THRILLID_USERNAMENoneThe username the service should use to authenticate with Thrill-ID. In a standard deployment, this should be set to thrillconnect
TCS_THRILLID_PASSWORDNoneThe password the service should use to authenticate with Thrill-ID. In a default deployment, this will start off as password and can be changed via Thrill-ID directly

Back to Top

Thrill-ID Service

Variable NameDefault ValueDescription
TID_LOG_LEVELinfoThe log level at which logs will be written. Possible values are info, debug, warn, trace
TID_WEB_HOST0.0.0.0The hostname to bind the web service to
TID_WEB_PORT80The port to bind the web service to
TID_MONGO_HOSTmongodb://localhostThe connection URI for the MongoDB server
TID_MONGO_DB_NAMEtestThe DB name for the Service (should usually be set to thrillid)
TID_MONGO_USERNAMENone[Optional] The username to use to authenticate with MongoDB
TID_MONGO_PASSWORDNone[Optional] The password to use to authenticate with MongoDB
TID_MONGO_RETRY_WRITEStrueFlag to set whether writes are retries when they fail
TID_REDIS_HOSTredis://localhostThe connection URI for REDIS. Possible schemas are:

- Standalone: redis://hostname:port

- Cluster: redis://hostname:port,redis://hostname2:port,..

- Sentinel: sentinel://hostname:port/master/replica or sentinel+tls://hostname:port/master/replica
TID_REDIS_DB0The Redis DB number to use
TID_REDIS_USERNAMENone[Optional] The REDIS username to use for authentication
TID_REDIS_PASSWORDNone[Optional] The REDIS password to use for authentication
TID_REDIS_SECUREfalse[Optional] Defines if the REDIS connection is secure or not
TID_REDIS_CLUSTERfalse[Optional] Defines if the REDIS connection is secure or not. For a standard Sentinel deployment, this variable should be set to false
TID_JWT_SECRETdefault-secret-for-this-serviceThe secret used when generating JWT tokens during account authentication
TID_JWT_STRICT_IP_CHECKtrueEnforce strict IP checking when refreshing tokens
TID_JWT_LIFETIME_SECS1800The lifetime of a JWT token
TID_JWT_REFRESH_LIFETIME_SECS300The amount of grace period allowed for a refresh token

Back to Top

BitBridge Service

Variable NameDefault ValueDescription
TT_LOG_LEVELinfoThe log level at which logs will be written. Possible values are info, debug, warn, trace
TT_WEB_HOST0.0.0.0The hostname to bind the web service to
TT_WEB_PORT80The port to bind the web service to
TT_MONGO_HOSTmongodb://localhostThe connection URI for the MongoDB server
TT_MONGO_DB_NAMEtestThe DB name for the Service (should usually be set to bitbridge)
TT_MONGO_USERNAMENone[Optional] The username to use to authenticate with MongoDB
TT_MONGO_PASSWORDNone[Optional] The password to use to authenticate with MongoDB
TT_MONGO_RETRY_WRITEStrueFlag to set whether writes are retries when they fail
TT_REDIS_HOSTredis://localhostThe connection URI for REDIS. Possible schemas are:

- Standalone: redis://hostname:port

- Cluster: redis://hostname:port,redis://hostname2:port,..

- Sentinel: sentinel://hostname:port/master/replica or sentinel+tls://hostname:port/master/replica
TT_REDIS_DB0The Redis DB number to use
TT_REDIS_USERNAMENone[Optional] The REDIS username to use for authentication
TT_REDIS_PASSWORDNone[Optional] The REDIS password to use for authentication
TT_REDIS_SECUREfalse[Optional] Defines if the REDIS connection is secure or not
TT_REDIS_CLUSTERfalse[Optional] Defines if the REDIS connection is secure or not. For a standard Sentinel deployment, this variable should be set to false
TT_THRILLID_HOSThttp://localhost:9000The URL for the Thrill-ID Service. For clustered environments, this should point to the DNS entry for the Thrill-ID Service on your internal load balancer
TT_THRILLID_USERNAMENoneThe username the service should use to authenticate with Thrill-ID. In a standard deployment, this should be set to bitbridge
TT_THRILLID_PASSWORDNoneThe password the service should use to authenticate with Thrill-ID. In a default deployment, this will start off as password and can be changed via Thrill-ID directly

Back to Top

ThrillOffice Service

Variable NameDefault ValueDescription
TO_LOG_LEVELinfoThe log level at which logs will be written. Possible values are info, debug, warn, trace
TO_WEB_HOST0.0.0.0The hostname to bind the web service to
TO_WEB_PORT80The port to bind the web service to
TO_MONGO_HOSTmongodb://localhostThe connection URI for the MongoDB server
TO_MONGO_DB_NAMEtestThe DB name for the Service (should usually be set to thrilloffice)
TO_MONGO_USERNAMENone[Optional] The username to use to authenticate with MongoDB
TO_MONGO_PASSWORDNone[Optional] The password to use to authenticate with MongoDB
TO_MONGO_RETRY_WRITEStrueFlag to set whether writes are retries when they fail
TO_REDIS_HOSTredis://localhostThe connection URI for REDIS. Possible schemas are:

- Standalone: redis://hostname:port

- Cluster: redis://hostname:port,redis://hostname2:port,..

- Sentinel: sentinel://hostname:port/master/replica or sentinel+tls://hostname:port/master/replica
TO_REDIS_DB0The Redis DB number to use
TO_REDIS_USERNAMENone[Optional] The REDIS username to use for authentication
TO_REDIS_PASSWORDNone[Optional] The REDIS password to use for authentication
TO_REDIS_SECUREfalse[Optional] Defines if the REDIS connection is secure or not
TO_REDIS_CLUSTERfalse[Optional] Defines if the REDIS connection is secure or not. For a standard Sentinel deployment, this variable should be set to false
TO_POTS_MONGO_HOSTmongodb://localhostThe connection URI for the MongoDB server for ThrillPots. Preferrably the connection string should indicate use of seconday instance for read purposes (?readPreference=secondary).
TO_POTS_MONGO_DB_NAMEtestThe DB name for ThrillPots Service (should usually be set to thrillpots)
TO_POTS_MONGO_USERNAMENone[Optional] The username to use to authenticate with MongoDB. A dedicated read-only user is recommended for this DB connection.
TO_POTS_MONGO_PASSWORDNone[Optional] The password to use to authenticate with MongoDB
TO_THRILLID_HOSThttp://localhost:9000The URL for the Thrill-ID Service. For clustered environments, this should point to the DNS entry for the Thrill-ID Service on your internal load balancer
TO_THRILLID_USERNAMENoneThe username the service should use to authenticate with Thrill-ID. In a standard deployment, this should be set to thrilloffice
TO_THRILLID_PASSWORDNoneThe password the service should use to authenticate with Thrill-ID. In a default deployment, this will start off as password and can be changed via Thrill-ID directly

Back to Top