Skip to content
This repository has been archived by the owner on Apr 17, 2021. It is now read-only.


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.


Build StatusGitHub licenseAll ContributorsPRs Welcome Code of Conduct

A open source developer community to promote local hackathons, conferences, and meetups, mentoring, calls for speakers, and collaboration.

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.


What things you need to install the software (latest versions) and how to install them

  • Docker - Used to build, ship, and run all services
  • Python - Dependency Management for backend services & scripts
  • Pipenv - A tool that aims to bring the best of all packaging worlds
  • Node - Used to create a UI via React, manage frontend dependencies

Setting up a local development environment

The following steps are required for first time setup. These steps will check out the repository, install the project dependencies, and the client dependencies needed for the React frontend and run the service on http://localhost. Note http://localhost will show a gateway error until the client has completed building (typically 1 minute for first time setup).

git clone
cd my-dev-space
npm install
cd services/client
npm install
cd ../../
docker-compose -f docker-compose-dev.yml up -d

Once the service is up and running, you will need to manually create the required tables in the database and install the optional seed data to complete the local Postgres setup.

docker-compose -f docker-compose-dev.yml run users-service python recreate_db
docker-compose -f docker-compose-dev.yml run users-service python seed_db
docker-compose -f docker-compose-dev.yml run events-service python recreate_db

On subsequent runs (when the above steps have been completed), you can apply new database migrations to your local service by running:

docker-compose -f docker-compose-dev.yml run users-service python db upgrade
docker-compose -f docker-compose-dev.yml run events-service python db upgrade

Alternatively, if you make a change to a model during development, you will need to create and commit a migration file for that service. As a best practice, migration files should be committed independently to code:

docker-compose -f docker-compose-dev.yml run users-service python db migrate
docker-compose -f docker-compose-dev.yml run events-service python db migrate

To load data into the service for development, the recommended solution is to use the load script within the scripts folder to populate the local database. Details on how to configure the script can be found in scripts/

cd scripts/
./ dev

And to tear down the local development stack, simply run:

docker-compose -f docker-compose-dev.yml down

If you wish to populate your local database with events from external services, you can use the steps outlined in the scripts README.

Running the tests

The following will run the unit tests for each respective service:

docker-compose -f docker-compose-dev.yml run client-test npm test
docker-compose -f docker-compose-dev.yml run users-service python test
docker-compose -f docker-compose-dev.yml run events-service python test

Running linting

docker-compose -f docker-compose-dev.yml run client npm run lint
docker-compose -f docker-compose-dev.yml run user-service py.test --black --pep8 --flakes -vv --mccabe --cov=project --cov-report=term-missing --junitxml=test-results/results.xml
docker-compose -f docker-compose-dev.yml run events-service py.test --black --pep8 --flakes -vv --mccabe --cov=project --cov-report=term-missing --junitxml=test-results/results.xml

Running code coverage

docker-compose -f docker-compose-dev.yml run users-service python cov

Local Postgres Connections

docker-compose -f docker-compose-dev.yml run events-db sh

psql postgres://postgres:postgres@events-db:5432/events_dev

Running one off scripts

Allows scripts/tasks to be run in environments specific docker containers.

docker-compose -f docker-compose-dev.yml build events-task
docker-compose -f docker-compose-dev.yml run events-task python scripts/

Debugging Python Applications

End to End tests

Integration tests used to evaluate all services behave correctly

npm install testcafe -g
export TEST_URL='http://localhost'
testcafe chrome e2e


Deployments to the staging and production environments require a PR to be opened against the staging/production branches; Upon successfully merging a PR into either branch; Travis CI will build, run, test, and deploy the changes to AWS ECS.

Built With

  • React - Javascript client framework
  • Flask - Python web framework
  • Postgres - Relational Database Management System
  • Docker - Build, run, and deploy services
  • Swagger - Generate API documentation
  • Nginx - high-performance HTTP server, reverse proxy


A list of contributors who participated in this project.

Kyle Harrison

πŸ’» πŸ“–

Adam Smith


Ewa G


Michael Grundie






Peter Stevenson


Alistair Brown



πŸ’» 🎨

Annette McCullough



This project is licensed under the MIT License - see the file for details


Please read for details on our code of conduct, and the process for submitting pull requests to us.