Skip to content

Latest commit

 

History

History
183 lines (148 loc) · 20.6 KB

CONFIGURATION.md

File metadata and controls

183 lines (148 loc) · 20.6 KB

Configuration

Thunderdome may be configured through environment variables or via a yaml file config.yaml located in one of:

  • /etc/thunderdome/
  • $HOME/.config/thunderdome/
  • Current working directory

Example yaml configuration file

http:
  domain: thunderdome.dev
db:
  host: localhost
  port: 5432
  user: thor
  pass: odinson
  name: thunderdome

Required configuration items

For Thunderdome to work correctly the following configuration items are required:

Option Environment Variable Description Default Value
http.domain APP_DOMAIN The domain/base URL for this instance of Thunderdome. Used for creating URLs in emails. thunderdome.dev
http.cookie_hashkey COOKIE_HASHKEY Secret used to make secure cookies secure. strongest-avenger
config.aes_hashkey CONFIG_AES_HASHKEY Secret used to encrypt passcode fields (e.g. Battle JoinCode, LeaderCode). therevengers

Database configuration

Thunderdome uses a Postgres database to store all data, the following configuration options exist:

Option Environment Variable Description Default Value
db.host DB_HOST Database host name. db
db.port DB_PORT Database port number. 5432
db.user DB_USER Database user id. thor
db.pass DB_PASS Database user password. odinson
db.name DB_NAME Database instance name. thunderdome
db.sslmode DB_SSLMODE Database SSL Mode (disable, allow, prefer, require, verify-ca, verify-full). disable
db.max_open_conns DB_MAX_OPEN_CONNS Max open db connections 25
db.max_idle_conns DB_MAX_IDLE_CONNS Max idle db connections in pool 25
db.conn_max_lifetime DB_CONN_MAX_LIFETIME DB Connection max lifetime in minutes 5

SMTP (Mail) server configuration

Thunderdome sends emails for user registration related activities, the following configuration options exist:

Option Environment Variable Description Default Value
smtp.enabled SMTP_ENABLED Whether or not sending emails (e.g. welcome, forgot password) is enabled true
smtp.host SMTP_HOST Smtp server hostname. localhost
smtp.port SMTP_PORT Smtp server port number. 25
smtp.user SMTP_USER Smtp server user.
smtp.pass SMTP_PASS Smtp server password.
smtp.secure SMTP_SECURE Set to authenticate with the Smtp server. true
smtp.identity SMTP_IDENTITY Smtp server authorization identity. Usually unset.
smtp.sender SMTP_SENDER From address in emails sent by Thunderdome. no-reply@thunderdome.dev

Configure Admin Email

To grant Admin access to Thunderdome for the first Admin user create an account first, then set the ADMIN_EMAIL environment variable or admin.email config file value. Upon the app starting up Thunderdome will read this value and set that user as ADMIN role.

Optional configuration items

Option Environment Variable Description Default Value
http.port PORT Which port to listen for HTTP connections. 8080
http.path_prefix PATH_PREFIX Prefix added to all application urls for shared domain use, in format of /{prefix} e.g. /thunderdome
http.secure_cookie COOKIE_SECURE Use secure cookies or not. true
http.backend_cookie_name BACKEND_COOKIE_NAME The name of the backend cookie utilized for actual auth/validation warriorId
http.frontend_cookie_name FRONTEND_COOKIE_NAME The name of the cookie utilized by the UI (purely for convenience not auth) warrior
http.write_tiemout HTTP_WRITE_TIMEOUT HTTP response write timeout in seconds 5
http.read_tiemout HTTP_READ_TIMEOUT HTTP request read timeout in seconds 5
http.idle_tiemout HTTP_IDLE_TIMEOUT HTTP request idle timeout in seconds 30
http.read_header_tiemout HTTP_READ_HEADER_TIMEOUT HTTP read header timeout in seconds 2
analytics.enabled ANALYTICS_ENABLED Enable/disable google analytics. true
analytics.id ANALYTICS_ID Google analytics identifier. UA-140245309-1
config.allowedPointValues CONFIG_POINTS_ALLOWED List of available point values for creating battles. 0, 1/2, 2, 3, 5, 8, 13, 20, 40, 100, ?
config.defaultPointValues CONFIG_POINTS_DEFAULT List of default selected points for new battles. 1, 2, 3, 5, 8 , 13, ?
config.show_warrior_rank CONFIG_SHOW_RANK Set to enable an icon showing the rank of a warrior during battle. false
config.avatar_service CONFIG_AVATAR_SERVICE Avatar service used, possible values see next paragraph gravatar
config.toast_timeout CONFIG_TOAST_TIMEOUT Number of milliseconds before notifications are hidden. 1000
config.allow_guests CONFIG_ALLOW_GUESTS Whether or not to allow guest (anonymous) users. true
config.allow_registration CONFIG_ALLOW_REGISTRATION Whether or not to allow user registration (outside Admin). true
config.allow_jira_import CONFIG_ALLOW_JIRA_IMPORT Whether or not to allow import plans from JIRA XML. true
config.default_locale CONFIG_DEFAULT_LOCALE The default locale (language) for the UI en
config.friendly_ui_verbs CONFIG_FRIENDLY_UI_VERBS Whether or not to use more friendly UI verbs like Users instead of Warrior, e.g. Corporate friendly false
config.allow_external_api CONFIG_ALLOW_EXTERNAL_API Whether or not to allow External API access false
config.user_apikey_limit CONFIG_USER_APIKEY_LIMIT Limit users number of API keys 5
config.show_active_countries CONFIG_SHOW_ACTIVE_COUNTRIES Whether or not to show active countries on landing page false
config.cleanup_battles_days_old CONFIG_CLEANUP_BATTLES_DAYS_OLD How many days back to clean up old battles, e.g. battles older than 180 days. Triggered manually by Admins . 180
config.cleanup_retros_days_old CONFIG_CLEANUP_RETROS_DAYS_OLD How many days back to clean up old retros, e.g. retros older than 180 days. Triggered manually by Admins . 180
config.cleanup_storyboards_days_old CONFIG_CLEANUP_STORYBOARDS_DAYS_OLD How many days back to clean up old storyboards, e.g. storyboards older than 180 days. Triggered manually by Admins . 180
config.cleanup_guests_days_old CONFIG_CLEANUP_GUESTS_DAYS_OLD How many days back to clean up old guests, e.g. guests older than 180 days. Triggered manually by Admins. 180
config.organizations_enabled CONFIG_ORGANIZATIONS_ENABLED Whether or not creating organizations (with departments) are enabled true
config.require_teams CONFIG_REQUIRE_TEAMS Whether or not creating battles, retros, and storyboards require being associated to a Team false
auth.method AUTH_METHOD Choose normal, header or ldap as authentication method. See separate sections on LDAP/header configurations. normal
feature.poker FEATURE_POKER Enable or Disable Agile Story Pointing (Poker) feature true
feature.retro FEATURE_RETRO Enable or Disable Agile Retrospectives feature true
feature.storyboard FEATURE_STORYBOARD Enable or Disable Agile Storyboard feature true

Open Telemetry Tracing

Thunderdome features Open Telemetry tracing to aid in monitoring application performance.

Option Environment Variable Description Default Value
otel.enabled OTEL_ENABLED Whether or not Open Telemetry tracing is enabled false
otel.service_name OTEL_SERVICE_NAME Service name of Thunderdome thunderdome
otel.collector_url OTEL_COLLECTOR_URL Open Telemetry supported tracing tool e.g. Uptrace, DataDog localhost:4317
otel.insecure_mode OTEL_INSECURE_MODE Disables client transport security for the exporter's gRPC connection false

Avatar Service configuration

Use the name from table below to configure a service - if not set, goadorable is used. Each service provides further options which then can be configured by a warrior on the profile page. Once a service is configured, drop downs with the different sprites become available. The table shows all supported services and their sprites. In all cases the same ID (ead26688-5148-4f3c-a35d-1b0117b4f2a9) has been used creating the avatars.

Name
goadorable (internal)
image
govatar (internal) male female
image image
dicebear male female human identicon bottts avataaars jdenticon gridy code
image image image image image image image image image
gravatar mp identicon monsterid wavatar retro robohash
image image image image image image
robohash set1 set2 set3 set4
image image image image

LDAP Configuration

If auth.method is set to ldap, then the Create Account function is disabled and authentication is done using LDAP. If the LDAP server authenticates a new user successfully, the Thunderdome user profile is automatically generated.

The following configuration options are specific to the LDAP authentication method:

Option Environment Variable Description
auth.ldap.url AUTH_LDAP_URL URL to LDAP server, typically ldap://host:port
auth.ldap.use_tls AUTH_LDAP_USE_TLS Create a TLS connection after establishing the initial connection.
auth.ldap.bindname AUTH_LDAP_BINDNAME Bind name / bind DN for connecting to LDAP. Leave empty for no authentication.
auth.ldap.bindpass AUTH_LDAP_BINDPASS Password for the bind.
auth.ldap.basedn AUTH_LDAP_BASEDN Base DN for the search for the user.
auth.ldap.filter AUTH_LDAP_FILTER Filter for searching for the user's login id. See below.
auth.ldap.mail_attr AUTH_LDAP_MAIL_ATTR The LDAP property containing the user's emil address.
auth.ldap.cn_attr AUTH_LDAP_CN_ATTR The LDAP property containing the user's name.

The default filter is (&(objectClass=posixAccount)(mail=%s)). The filter must include a %s that will be replaced by the user's login id. The mail_attr configuration option must point to the LDAP attribute containing the user's email address. The default is mail. The cn_attr configuration option must point to the LDAP attribute containing the user's full name. The default is cn.

On Linux, the parameters may be tested on the command line:

ldapsearch -H auth.ldap.url [-Z] -x [-D auth.ldap.bindname -W] -b auth.ldap.basedn 'auth.ldap.filter' dn auth.ldap.mail auth.ldap.cn

The -Z is only used if auth.ldap.use_tls is set, the -D and -W parameter is only used if auth.ldap.bindname is set.

Header auth Configuration

If auth.method is set to header, then the Create Account function is disabled and authentication is done using headers. The assumption being that the only access to thunderdome is via a reverseproxy

The following configuration options are specific to the LDAP authentication method:

Option Environment Variable Default Description
auth.header.usernameHeader AUTH_HEADER_USERNAME_HEADER Remote-User The header to use for the user's username
auth.header.emailHeader AUTH_HEADER_EMAIL_HEADER Remote-Email The header to use for the user's email