Skip to content
Framework for a web service that provides an API for aggregated ETP outcomes
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


Coverage Status

tpot-api is a framework for a web service that provides an API for aggregated TPOT outcomes. The default setting for the server is Heroku with Heroku Postgres database. The goal is for every institution to have an easy deployment for their TPOT outcomes that could be used in more sophisticated tools, analyses and downstream applications by developers.

live demo (We initially called it ETP-API)

Design and Documentation

The API spec can be publicly viewed here and is hosted here.

The folder .openapi was generated automatically by SwaggerHub. We have set up Github Sync for the API spec on Swaggerhub. It promises to automatically update the spec on Github with changes done in SwaggerrHub. The API design and documentation process, therefore, is that all stakeholders collaborate on SwaggerHub and the update is synced on Github upon save.


We noted however that this integration is still buggy (It doesn't sync with Github on save). The integration works well for setting up this workflow for a new repo. So we activated Github Push for the syncing. The spec file is at .openapi/swagger.yaml.

To adopt this workflow

For a similar workflow, you'll find that the docs in Github Push and Github Sync are quite straight forward.

Be sure to set:

  • a separate branch other that the main ones (In our case we chose SWAGGERHUB)
  • swagger output folder as .openapi and
  • swagger file as swagger.yaml

Quick run

  • Have docker installed
  • Run docker-compose up and get to localhost:8080
  • To stop this server, enter Ctrl+C

Quick Deployment

One-click deploy


Quick Start for Developers

1. Prerequisites

  • Have a Heroku account.
  • Have Heroku CLI installed.
  • Have a data.csv file in /deploy directory that matches the schema as example_data.csv in /test directory.

2. Clone repository

tpot-api is available through cloning the repository and then working from the repository root.

git clone
cd tpot-api

3. Virtualenv

tpot-api depends on python3, so create a virtual environment using a python3 executable. Then activate the virtualenv.

virtualenv venv -p /usr/bin/python3
source venv/bin/activate

4. Python requirements

Install requirements.

pip install -r requirements.txt

5. Running tests

nosetests --with-coverage -v --cover-package=tpot_api

6. Run and deploy

Run the and enter the right information for Heroku username and password. The tpot-api server will be deployed on Heroku.


7. Automating deployment using habitat

Habitat helps package an app or service into containers that can be run in any infrastructure, without committing to a specific container format or platform.

Installing habitat

To install habitat, simply download the binary.

  • Unzip hab into /usr/local/bin. To do this:
    • Unzip the downloaded folder
    • Navigate to the unzipped folder by running cd followed by the file location
      • For example: cd /Users/Rachel/Downloads/hab-0.28.0-20170729010833-x86_64-darwin (If you're using a Mac, you can insert the location by dragging the unzipped file into the terminal)
    • Run cp hab /usr/local/bin
      • If you receive an error saying Permission Denied, run sudo cp hab /usr/local/bin
  • Run sudo chmod a+x hab to make it executable.
  • You'll also need docker installed if on Mac. Find docker here
  • To confirm if habitat is installed, re-open your terminal and type hab then press enter. You should see a list menu with all the habitat options available. Moving on swiftly!

Setup a habitat origin

  • Run hab setup and set the origin name to brighthive.
  • Go to Settings on your github account and create a Personal Access Token under Developer Settings. Here's a link to get you there.

The GitHub personal access token needs information provided from the user:email and read:org OAuth scopes. Habitat uses the information provided through these scopes for authentication and to determine features based on team membership.

This is how it should look like when running the setup: screenshot 2017-07-28 18 18 26

Running tpot-api using habitat

  • Cd into the repo's directory
cd tpot-api
  • Enter the habitat studio
hab studio enter

This is an awesome isolated environment for building great things so that when building, it doesn't affect anything on your computer. Let's go ahead and build the tpot-api!

  • Inside the studio, run the build command to execute the tpot-api plan
[5][default:/src:0]# build

When finished building, you should see this message tpot-api: I love it when a comes together.

The build bundles up the tpot-api source code, dependencies, runtime and other server configurations into a habitat .hart package. This package can now be exported to docker.

In linux environments, the package can then be run directly using this simple command:

$ hab start brighthive/tpot-api

Exporting to docker

You can export the created .hart package into a docker container using the hab pkg export docker command as follows:

[5][default:/src:0]# hab pkg export docker brighthive/tpot-api

All systems go!

After exiting the studio by typing exit, run the docker container as follows:

$ docker run -it -p 8080:8080 brighthive/tpot-api

We're cooking with gas! 🔥 🚀


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

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.