Thunderdome Planning Poker

Thunderdome is an open source agile planning poker tool in the theme of Battling for points that helps teams estimate stories.

• Planning Sessions are Battles
• Users are Warriors
• Stories are Plans

Uses WebSockets and Svelte frontend framework for a truly reactive UI experience

Running in production

Use latest docker image

docker pull stevenweathers/thunderdome-planning-poker

Use latest released binary

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:

Database configuration

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

SMTP (Mail) server configuration

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

Optional configuration items

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)
govatar (internal)	male	female
dicebear	male	female	human	identicon	bottts	avataaars	jdenticon	gridy	code
gravatar	mp	identicon	monsterid	wavatar	retro	robohash
robohash	set1	set2	set3	set4

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:

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.

Developing

Building and running with Docker (preferred solution)

Using Docker Compose

docker-compose up --build

Using Docker without Compose

This solution will require you to pass environment variables or setup the config file, as well as setup and manage the DB yourself.

docker build ./ -f ./build/Dockerfile -t thunderdome:latest
docker run --publish 8080:8080 --name thunderdome thunderdome:latest

Building

To run without docker you will need to first build, then setup the postgres DB, and pass the user, pass, name, host, and port to the application as environment variables or in a config file.

DB_HOST=
DB_PORT=
DB_USER=
DB_PASS=
DB_NAME=

Install dependencies

go get
npm install

Build with Make

make build

OR manual steps

Build static assets

npm run build

Build for current OS

go build

Let the Pointing Battles begin!

Run the server and visit http://localhost:8080

Adding new Localizations

Using svelte-i18n Thunderdome now supports Locale selection on the UI (Default en-US)

Adding new locale's involves just a couple of steps.

1. First add the locale dictionary json files in frontend/public/lang/default/ and frontend/public/lang/friendly/ by copying the en.json and just changing the values of all keys
2. Second, the locale will need to be added to the locales list used by switcher component in frontend/config.js locales object

Donations

For those who would like to donate a small amount for my efforts or monthly hosting costs of Thunderdome.dev I accept paypal.