Skip to content
Docker Turnkey for PHP/MongoDB service
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.

iReceptor Turnkey

The iReceptor Turnkey is a quick and easy mechanism for a researcher or research group to install and manage an AIRR-seq data repository. In addition, the included iReceptor Web Service makes it possible to integrate the repository into the AIRR Data Commons.

For more information, refer to the iReceptor Turnkey section on the main iReceptor web site.

The remainder of this document provides directions on how to install and run the iReceptor Turnkey.

What is it?

  • a database
  • a web application exposing that database through the iReceptor API
  • some scripts to load your data into the database

iReceptor Service Turnkey Architecture

How does it work?

Docker containers are used to make the installation and future updates clean and simple. For more information, see How it works.


Download the code (from the production branch) and excute the install script. It will take 10-30 min, depending on the download speed of the Docker images.

# download the code
git clone --branch production

# launch the installation (multiple Docker images will be downloaded from DockerHub)
cd turnkey-service-php

Check it's working

Go to http://localhost/v2/samples in your browser (if necessary, replace "localhost" with your server URL).

This returns the list of samples in your database by querying the web application at /v2/samples, which is an entry point of the iReceptor API. An empty array [] is returned because the database is currently empty.

You can also use the command line:

curl -X POST -H "Content-Type: application/x-www-form-urlencoded" "http://localhost/v2/samples"

Loading data

General procedure

  1. load the metadata associated with a study that has generated sequence data.
  2. load the sequence annotations (from imgt, mixcr, etc).

Quick example: loading the test data

  1. Load the metadata file test_data/metadata_mixcr.csv:
scripts/ test_data/metadata_mixcr.csv

To check it worked, go to http://localhost/v2/samples or execute:

curl -X POST -H "Content-Type: application/x-www-form-urlencoded" "http://localhost/v2/samples"
  1. Load the associated sequence annotations file test_data/rearrangements_mixcr.txt:
scripts/ mixcr test_data/rearrangements_mixcr.txt

To check it worked, go to http://localhost/v2/sequences_summary or execute:

curl -X POST -H "Content-Type: application/x-www-form-urlencoded" "http://localhost/v2/sequences_summary"

Note: to load IMGT or AIRR annotations, replace the mixcr parameter by imgt or airr. Example:

scripts/ imgt <IMGT file>

Congratulations ☺️ You can now reset the turnkey database and load your own data.

Loading large data sets

The above scripts can be used to load large data sets. In particular, the script can be used to load many rearrangement files in a row. We recommend following a well structured data curation process to help ensure data provenance around your data management. Please refer to the iReceptor Curation process and the iReceptor Curation GitHub repository for more information on recommended data curation approaches.

Assuming all data for a study can be found in a single directory, it is possible to utilize the two commands described above to load the entire study data. Assuming your data is in a folder called STUDY_DATA, the study metadata is stored in a metadata file called METADATA.csv, and all of your rearrangement files are MiXCR .txt files, you can do the following:

  1. To load your Repertiore Metadata use the scrip as above:
  1. To load your rearrangement data, use the as given below:
scripts/ mixcr STUDY_FOLDER/*.txt

It is important to note that depending on the size of the data in your rearrangement files, loading the rearrangements can take a very long time. As a result, it is good practice to use the Unix "nohup" command to control the rearrantement loading. The Unix nohup command allows you to run a long running command in the background, redirects the output of that command to a file, and allows you to log out and come back to check on the progress of your command later. You would use the nohup command as follows:

nohup scripts/ mixcr STUDY_FOLDER/*.txt > rearrangement.log &

Also note that both the and the command produce log files for every file that they process. If you want to view the log files simply refere to the files in the log directory. Log files are named using date and the file that was processed.

More information

Contact us


You can’t perform that action at this time.