Skip to content
Encouraging OpenStreetMap mappers with badges, graphs & stats! 🕹
Branch: develop
Clone or download
Latest commit f9d08fa Jul 19, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci remove old eslint dependencies, update scripts Nov 12, 2018
api Fix changeset counts in campaign table Jul 19, 2019
deployment/centos Add teams env variables to READMEs Jun 7, 2019
docusaurus Merge branch 'develop' into feature/tm-extra-params May 15, 2019
pages Fix language on homepage Jul 19, 2019
scripts merge dependencies into one package.json, get frontend tests running,… Nov 7, 2018
static Merge branch 'develop' into feature/pdfkit Mar 26, 2019
styles Merge branch 'develop' into feature/teams-update Jun 6, 2019
tests lint fix May 15, 2019
.env.sample Merge May 29, 2019
.eslintignore Fix lint Jan 23, 2019
.eslintrc.json fix remaining errors Nov 12, 2018
Procfile-dev Country clock process to sum edit counts and add to Countries table Dec 6, 2018 Add teams env variables to READMEs Jun 7, 2019
docker-compose.yml merge dependencies into one package.json, get frontend tests running,… Nov 7, 2018
package.json 1.3.5 Jul 19, 2019
server.js Add mock mbtiles server Feb 12, 2019

Scoreboard 🗺🎯

Engaging and encouraging mappers of OpenStreetMap by rewarding contributions, promoting campaigns, and reporting current mapper statistics

🔨 Development


  • Node 8.4
  • Postgres 9.5+
  • Yarn
  • Docker (for development work)

To set the Node version as specified above:

 $ brew install nvm
 $ nvm use

See this tutorial for details and instructions for installing PostgreSQL on your operating system


Scoreboard depends on three external services/APIs for statistics and functionality:

  • OSMesa is a toolkit for processing large amounts of OSM vector data and turning them into stats (e.g: km of road added by user by country)
  • Scoreboard pulls campaigns from the Tasking Manager and uses the campaign hashtags to pull campaign specific aggregations from OSMesa
  • OSM Teams is a service that allows Scoreboard users to create teams and assign campaigns to a team.

Env file

There should be an env file in the root project directory with the following environment variables.

For development simply run: cp .env.sample .env. In development, the Osmesa service is mocked, so the environment variables OSMESA_API is not required.

name description
NODE_ENV The configuration to use, "test", "development" or "production"
OSMESA_API URL to the OSMESA http server that serves out statistics
APP_URL URL where the site will be hosted
OSM_CONSUMER_KEY An Oauth Key/Secret pair to authenticate with OSM
OSM_CONSUMER_SECRET An Oauth Key/Secret pair to authenticate with OSM
OSM_DOMAIN OSM endpoint (defaults to
OSM_TEAMS_SERVICE Location of the OSM teams API
OSM_TEAMS_CLIENT_ID Client id for OSM Teams authentication
OSM_TEAMS_CLIENT_SECRET Client secret for OSM Teams authentication
OSM_TEAMS_TOKEN_HOST Location of OSM Teams token endpoint (e.g http://osm-teams)
OSM_TEAMS_TOKEN_PATH Location of OSM Teams token path (e.g /oauth2/token)
OSM_TEAMS_AUTHZ_HOST Location of OSM Teams authorization endpoint (e.g http://osm-teams)
OSM_TEAMS_AUTHZ_PATH Location of OSM Teams authorization path (e.g /oauth2/auth)
SESSION_SECRET A secret phrase to sign session tokens
DATABASE_URL The location of the postgres database

Once the Scoreboard app is running, you can add a tasking manager in the admin panel

Installation and Dev

 $ yarn

Postgres Setup

Create and Run the database

 $ docker-compose up -d

This command will create and run the database on port 5433. The database files are stored under .tmp folder.

If you are running the command for the first time, you should wait until the database is created. This can take a few minutes.

To start with a new database with no data, stop the command, remove the .tmp folder and run the command again.

Run migrations

Set up the database schema by running:

 $ yarn migrate

You can rollback migrations with yarn rollback.

Populate Data

For the frontend and the API to work, you must have the data loaded on the local database.

To generate fake user and campaign data run:

 $ yarn seed

Create an admin user

To be able to develop admin pages you'll need to have an admin user.

Make your user an admin by running:

./api/bin/scoreboard create-admin-user --username {your osm username}

If you were already logged in, log out and log back in, then you'll see an "admin" link in the menu in the top right.


This command will start both the frontend and the api together

 $ yarn dev


Tests for the API endpoints and related code are stored in api/tests/ and UI tests are stored in tests/. To run both:

$ yarn test

Test the UI and API separately using yarn test-ui and yarn test-api.


Lint the code using:

 $ yarn lint

You can automatically fix some lint errors using yarn lintfix.

Generating Docs

If you make changes to the API documentation make sure to update the README for the API which is auto-generated from the swagger YAML by running:

 $ yarn docs


To use scoreboard in production follow these steps:

  1. Make sure you have all the requirements.
  2. Install dependencies: yarn
  3. Setup a production Postgres database
  4. Create the database by running these commands.
  5. Setup an .env file with correct values -> example.
  • make sure to set NODE_ENV=production in your .env file
  1. Run the migrations: npm run migrate
  2. Add initial data to the database (skip if the database already has data) npm run seed
  3. [OPTIONAL] Preload list of users npm run users
  4. Populate stats: npm run clocks
  5. [OPTIONAL] Assign admin users by running ./api/bin/scoreboard create-admin-user --osm-id {your-id}
  6. Build: npm run build
  7. Launch the server: node server.js
You can’t perform that action at this time.