A Python application to build, configure, and deploy QIIME and its dependencies on Linux systems.

To run qiime-deploy, you will first need to grab a configuration file. The configuration file will tell qiime-deploy what packages it should install. You can find many QIIME deployment configuration files in the qiime-deploy-conf project here as well as a description of all possible options and the configuration file format. There are also various other configuration files included for installing other QIIME-related projects/tools.

Also, while qiime-deploy downloads, builds, and installs many of QIIME's dependencies, it does expect common packages to already be installed on your system. For example, on Debian Lenny, a complete QIIME install depends on the following packages:

libgsl0-dev openjdk-6-jdk libxml2 libxslt1.1 libxslt1-dev ant git
subversion build-essential zlib1g-dev libpng12-dev libfreetype6-dev mpich2
libreadline-dev gfortran unzip libmysqlclient16 libmysqlclient-dev ghc
python-dev libncurses5-dev

After the deploy completes it will generate an activate.sh file in the base deploy directory. It is necessary to source that file in order to set the environment created by qiime-deploy. For example, if the deploy directory is /opt/qiime/ you will need to run the following command:

source /opt/qiime/activate.sh

Note: By default, qiime-deploy will append the above line to your ~/.bashrc. This is done so that you do not need to run the command each time you open a new terminal. To disable this behavior, you will need to modify the qiime-deploy conf file (see the qiime-deploy-conf project here for a description of the options you can tweak).

While qiime-deploy may work on various Linux distributions, it has been most heavily tested on Ubuntu 11.10 and 12.04 LTS (64-bit) systems. Thus, we provide a short guide to setting up your Ubuntu system so that it can run qiime-deploy.

In order to ensure that you have the required prerequisite packages installed on your Ubuntu system, perform the following steps:

1. Uncomment the universe and multiverse repositories from /etc/apt/sources.list. You can use your favorite text editor but we suggest pico for simplicity. Note that at the bottom of the screen you will have the commands to save, exit, etc..

    sudo pico /etc/apt/sources.list
   

2. Install the qiime-deploy dependencies on your machine. This step requires admin (sudo) access. If you do not have sudo access, you must ask your system administrator to grant you sudo access, or to run these steps for you. In general, all of this software should already be installed but it may not be. It's therefore best to run this command before the following step.

   For Ubuntu 11.10:

    sudo apt-get --force-yes -y install python-dev libncurses5-dev libssl-dev libzmq-dev libgsl0-dev openjdk-6-jdk libxml2 libxslt1.1 libxslt1-dev ant git subversion build-essential zlib1g-dev libpng12-dev libfreetype6-dev mpich2 libreadline-dev gfortran unzip libmysqlclient16 libmysqlclient-dev ghc
   

   For Ubuntu 12.04:

    sudo apt-get --force-yes -y install python-dev libncurses5-dev libssl-dev libzmq-dev libgsl0-dev openjdk-6-jdk libxml2 libxslt1.1 libxslt1-dev ant git subversion build-essential zlib1g-dev libpng12-dev libfreetype6-dev mpich2 libreadline-dev gfortran unzip libmysqlclient18 libmysqlclient-dev ghc
   

The following subsections include examples of common qiime-deploy use cases.

Note: At the time of this writing, QIIME 1.6.0 is the latest public release, and QIIME 1.6.0-dev is the development version of QIIME. As newer versions of QIIME are released we will include conf files for each new version in the qiime-deploy-conf project. The following usage examples will work for any version of QIIME (unless otherwise noted), but you will need to supply the correct conf file as input to qiime-deploy.

To see the available options provided by qiime-deploy, run the following command:

python qiime-deploy.py -h

To install QIIME 1.6.0 under $HOME/qiime_software/, run the following commands. These commands assume you have already set up your system following the directions above and that you are in your home directory. You can change these paths as you like (e.g. to install QIIME under a different directory), but you will need to modify the commands we provide to use the new paths.

git clone git://github.com/qiime/qiime-deploy.git
git clone git://github.com/qiime/qiime-deploy-conf.git
cd qiime-deploy/
python qiime-deploy.py $HOME/qiime_software/ -f $HOME/qiime-deploy-conf/qiime-1.6.0/qiime.conf --force-remove-failed-dirs
source $HOME/.bashrc

To test that you have a functioning QIIME install, run the following command:

print_qiime_config.py -t

qiime-deploy will create a QIIME config file under $HOME/qiime_software/qiime_config as part of the deployment process. If you would like to edit this file to further customize your QIIME install, feel free to do so. If you rerun qiime-deploy using the same deploy directory (in this example, $HOME/qiime_software/), your old QIIME config will be renamed to qiime_config.bak and the new one will be named qiime_config.

To install the development version of QIIME (currently 1.6.0-dev), use the same commands as above, but supply a different qiime-deploy conf file as input:

python qiime-deploy.py $HOME/qiime_software/ -f $HOME/qiime-deploy-conf/qiime-1.6.0-dev/qiime.conf --force-remove-failed-dirs --force-remove-previous-repos

You may install more than one version of QIIME on your system. To do so, you will need to install each version in its own deploy directory. For example, if you would like to have QIIME 1.6.0 and QIIME 1.6.0-dev, you could install QIIME 1.6.0 under $HOME/qiime-1.6.0/ and QIIME 1.6.0-dev under $HOME/qiime-1.6.0-dev/. To activate the QIIME version that you would like to use, source the appropriate activate.sh file. For example, to activate QIIME 1.6.0-dev, you would run the following command:

source $HOME/qiime-1.6.0-dev/activate.sh

If you are unsure of what version of QIIME you currently have activated, run the following command:

print_qiime_config.py -t

If you want to change the version of QIIME in an existing qiime-deploy install, you can simply run qiime-deploy with the conf file corresponding to the version that you'd like to upgrade/downgrade to. Make sure to specify the existing deploy directory in order to upgrade/downgrade your existing install. If you specify a new directory, you will end up with multiple versions of QIIME installed on your system (which is okay; see the section above for more details).

When I run print_qiime_config.py -t, I get a test failure for usearch. How can I fix this?

qiime-deploy cannot install usearch due to licensing restrictions. You can obtain the usearch binary here. Please be sure to download the currently supported version for your version of QIIME. If you are using the latest stable release of QIIME, you can find the required usearch version here.

Rename the executable to usearch and make sure it is somewhere that is in your PATH environment variable. You also need to ensure that execute permissions are set. For example:

mkdir $HOME/bin
mv <path to usearch executable> $HOME/bin/usearch
chmod +x $HOME/bin/usearch
echo 'export PATH=$HOME/bin:$PATH' >> $HOME/.bashrc
(open a new terminal)
usearch --version
print_qiime_config.py -t

Does qiime-deploy work on 32-bit operating systems?

No, qiime-deploy only supports 64-bit operating systems. If you run qiime-deploy on a 32-bit system, it may correctly install some dependencies, but when running print_qiime_config.py -t to check that your QIIME install is functioning, you may receive strange errors similar to the following:

ELF : not found
Syntax error: word unexpected (expecting ")")
Syntax error: Unterminated quoted string

Upgrading your operating system to 64-bit and rerunning qiime-deploy will solve this issue.

1. New applications with custom build types should be added to lib/custom.py. Both a function and a call to that function from custom.custom_deploy should be added.

2. Any custom finalization code should be called from lib/custom.py in custom.custom_finalize.

3. If additional options need to be added to any of the config file sections, they will likely need to be added to the init of the Application class in lib/application.py.

4. New generic build processes will need to be added to the Application class in lib/application.py. Additionally, the generic utility functions required should be added to lib/util.py.