You have a few options to have a ToxicBuild instance running.

Using Docker

The easiest way to have a ToxicBuild local installation is to use Docker. So, with docker installed on your system, first clone the code:

$ git clone
$ cd toxicbuild

And then run the ./build-scripts/ create-local command

$ ./build-scripts/ create-local
- Pulling required images

- Creating toxicbase image. Be patient.

- Creating toxicslave
- Creating toxicoutput
- Creating toxicmaster
  password: 123
- Creating toxicscheduler
- Creating toxicpoller
- Creating toxicintegrations
- Creating toxicweb

Now you can start with ./build-scripts/ start-local

$ ./build-scripts/ start-local

And access http://localhost:8888/ using your browser.

Using pip

ToxicBuild is written in Python, and runs in Python3.6 and later. It uses MongoDB to store data, rabbitmq for queues, zookeeper for coordination and git as vcs. You must have these installed. In a Debian system, use the following command:

sudo apt-get install mongodb rabbitmq zookeeperd

If you want to be able to build c extensions for speed, install the Python header files, a C compiler libffi and libyaml.

sudo apt-get install build-essential libffi-dev python3.7-dev libyaml-dev

After the installation of the external dependencies you can install toxicbuild using pip:

$ pip install toxicbuild

Now that toxicbuild is installed we need to create a new environment


Create a new environment using the command toxicbuild create.

$ toxicbuild create ~/ci
Creating root_dir `ci/slave` for toxicslave
Toxicslave environment created with access token: mI4AHDl0LjzTrD1RieX64xp1xWrXhoiGgdedFJ5IRvg
Creating root_dir `ci/output` for toxicoutput
Creating root_dir `ci/master` for toxicmaster
password: 123
Toxicmaster environment created with access token: wq7dUahnE_EkveLIH1R9KsDg2qT0rHSfljQqh1g3iB8
Creating root_dir `ci/integrations` for toxicintegrations
Creating root_dir ci/ui
Toxicui environment created for web

And now you can start toxicbuild with the command toxicbuild start:

$ toxicbuild start ~/ci
Starting toxicslave
Starting toxicmaster
Starting toxicpoller
Starting toxicscheduler
Starting output web api on port 9432
Starting integrations on port 9999

Installing only toxicslave

One toxicbuild installation can handle multiple slaves so now lets install only toxicslave and use supervisor to start toxicslave on startup.

For the slave we don’t need mongo, rabbitmq or zookeeper, so we simply install toxicbuild

$ pip install toxicbuild

Now we create a toxicslave environment

$ toxicslave create ~/ci/slave
Creating root_dir `ci/slave` for toxicslave
Toxicslave environment created with access token: xXE2enJ-O1YcSx8vurLyTawGds_bkJ79i6-LShVEPjA

Save this access token as it can’t be recovered later.

This is an example of a minimal supervisor config:

command=/home/ec2-user/venv/bin/toxicslave start /home/ec2-user/ci/slave