Qiita is pip installable, but depends on specific versions of python and non-python packages that must be installed first. We strongly recommend using virtual environments; a popular solution to manage them is miniconda, a lightweight version of the virtual environment, python distribution, and package manager anaconda. These instructions will be based on miniconda.
Download the appropriate installer here corresponding to your operating system and execute it.
Next, ensure conda is up-to-date.
conda update condaSetup a virtual environment in conda named qiita by executing the following:
conda config --add channels conda-forge
conda create -q --yes -n qiita python=3.9 pip libgfortran numpy nginx cython redisThough these instructions use the newly created qiita conda environment, the concepts apply to managing conda environments in general.
Activate your newly created virtual environment for qiita whenever you want to run or develop for it:
source activate qiitaAfter activating your new environment, you should see this kind of output when you run which python, indicating that the python command now refers to the python binary in your new virtual environment, rather than a previous global default such as /usr/bin/python. For example, assuming you installed miniconda in /Users/your_username/:
$ which python
/Users/your_username/miniconda2/envs/qiita/bin/python
(qiita)
If you don't see this output, your $PATH variable was setup incorrectly or you haven't restarted your shell. Consult the conda documentation.
As long as you are in the active qiita environment, commands such as pip install or python will refer to and be contained within this virtual environment.
When you want to deactivate your current conda environment, e.g. to return to a different project or back to your global python and pip packages, run:
source deactivate- PostgreSQL (currently using v13)
- redis-server (we have tested most extensively with 2.8.17)
- [webdis] (https://github.com/nicolasff/webdis) (latest version should be fine but we have tested the most with 9ee6fe2 - Feb 6, 2016)
There are several options to install these dependencies depending on your needs:
- We suggest installing the exact versions in these instructions by following the instructions of the provided links and making them globally available in your machine. However, this might interfere with other apps that might require different versions.
- Alternatively, you could install them via conda. However, the conda repository may not have the exact versions of these dependencies that you want.
- You could setup a full development environment with Vagrant, and continue using conda under it to primarily manage python dependencies. Note that we don't cover Vagrant in these instructions.
The following instructions have been adapted from this site and tested on Ubuntu v20.04.4 for Postgres v13.
First, ensure that you have updated packages and reboot the system with:
sudo apt update && sudo apt -y full-upgrade
[ -f /var/run/reboot-required ] && sudo reboot -fYou can reboot the system with sudo reboot in case any packages were updated.
Next, we need to add the Postgres repository to our system:
sudo apt update
sudo apt install curl gpg gnupg2 software-properties-common apt-transport-https lsb-release ca-certificates git
curl -fsSL https://www.postgresql.org/media/keys/ACCC4CF8.asc|sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/postgresql.gpg
echo "deb http://apt.postgresql.org/pub/repos/apt/ `lsb_release -cs`-pgdg main" |sudo tee /etc/apt/sources.list.d/pgdg.listAdding the repository has added many different packages, which allows us to now install Postgres v13 with the following commands:
sudo apt update
sudo apt install postgresql-13 postgresql-client-13Now, we need to reconfigure the pg_hba.conf file and change all occurrences of md5 and peer to trust. You can access the file with:
sudo vim /etc/postgresql/13/main/pg_hba.confTo make sure all changes have been reflected, restart the Postgres server:
sudo service postgresql restartInstalling Postgres is now complete. Note that you will need to start the Postgres server every time you start the Qiita server. You can do this with the following command:
sudo service postgresql startFor Mac OS X, it is strongly encourage to install Postgres through the Postgres.app. We recommend using Postgres.app versions 9.5 or 13, as instructions were tested most extensively with these versions.
You'll then need to ensure that the postgres binaries (for example, psql) are in your executable search path ($PATH environment variable). If you are using Postgres.app on OS X, you can do this by running the following, though you may have to replace~/.bash_profilewith ~/.zshrc if you're using zshell rather than the built-in bash, and you may have to change the version number Versions/9.3/ to the exact one that you are installing:
echo 'export PATH="$PATH:/Applications/Postgres.app/Contents/Versions/9.5/bin/"' >> ~/.bash_profile
source ~/.bash_profileAssuming you have homebrew installed, you can install the latest version of the redis-server as follows:
brew update
brew install homebrew/versions/redis28Alternatively, you can sudo install redis:
sudo apt-get install redis-serverNote that this package is OPTIONAL and this is the only package that assumes that Qiita is already installed (due to library dependencies). Also, that the general suggestion is to have 2 redis servers running, one for webdis/redbiom and the other for Qiita. The reason for multiple redis servers is so that the redbiom cache can be flushed without impacting the operation of the qiita server itself.
The following instructions install, compile and pre-populates the redbiom redis DB so we assume that redis is running on the default port and that Qiita is fully installed as the redbiom package is installed with Qiita.
git clone https://github.com/nicolasff/webdis
pushd webdis
make
./webdis &
popd
# note that this assumes that Qiita is already installed
fp=`python -c 'import qiita_db; print qiita_db.__file__'`
qdbd=`dirname $fp`
redbiom admin scripts-writable
redbiom admin create-context --name "qiita-test" --description "qiita-test context"
redbiom admin load-sample-metadata --metadata ${qdbd}/support_files/test_data/templates/1_19700101-000000.txt
redbiom admin load-sample-metadata-search --metadata ${qdbd}/support_files/test_data/templates/1_19700101-000000.txt
redbiom admin load-sample-data --table ${qdbd}/support_files/test_data/processed_data/1_study_1001_closed_reference_otu_table.biom --context qiita-test --tag 1
Clone the git repository with the development version of Qiita into your current directory:
git clone https://github.com/qiita-spots/qiita.gitNavigate to the cloned directory and ensure your conda environment is active:
cd qiita
source activate qiitaIf you are using Ubuntu or a Windows Subsystem for Linux (WSL), you will need to ensure that you have a C++ compiler and that development libraries and include files for PostgreSQL are available. Type cc into your system to ensure that it doesn't result in program not found. If you use the the GNU Compiler Collection, make sure to have gcc and g++ available. The following commands will install a C++ compiler and libpq-dev:
sudo apt install gcc g++ # alternatively, you can install clang instead
sudo apt-get install libpq-devInstall Qiita (this occurs through setuptools' setup.py file in the qiita directory):
pip install . --no-binary redbiomNote that if you get any errors or warnings with 'certifi', you can add the --ignore-installed tag to the command above.
At this point, Qiita will be installed and the system will start. However, you will need to install plugins in order to process any kind of data. For a list of available plugins, visit the Qiita Spots github organization. Each of the plugins have their own installation instructions, we suggest looking at each individual .github/workflows/qiita-plugin-ci.yml file to see detailed installation instructions. Note that the most common plugins are:
After these commands are executed, you will need to:
Move the Qiita sample configuration file to a different directory by executing:
cp ./qiita_core/support_files/config_test.cfg ~/.qiita_config_test.cfgNote that you will need to change BASE_URL = https://localhost:8383 to BASE_URL = https://localhost:21174 in the new copy of the configuration file if you are not using NGINX. Additionally, you will also need to change all URLs that start with /home/runner/work/qiita/qiita/... into wherever your qiita directory is (e.g. /home/<username>/qiita/...).
Set your QIITA_CONFIG_FP environment variable to point to that file (into .bashrc if using bash; .zshrc if using zshell):
echo "export QIITA_CONFIG_FP=$HOME/.qiita_config_test.cfg" >> ~/.bashrc
source ~/.bashrc
# Re-enable conda environment for qiita
source activate qiitaIf you are working on Mac OS X or WSL, you will need to start the redis server with the following command before making a test environment:
redis-server --daemonize yes --port 7777Next, make a test environment:
qiita-env make --no-load-ontologiesFinally, redbiom relies on the REDBIOM_HOST environment variable to set the URL to query. By default is set to Qiita redbiom public repository. To change it you could do:
export REDBIOM_HOST=http://my_host.com:7379NGINX is not a requirement for Qiita development but it's highly recommended for deploys as this will allow us
to have multiple workers. Note that we are already installing NGINX within the Qiita conda environment; also,
that Qiita comes with an example NGINX config file: qiita_pet/nginx_example.conf, which is used in the Travis builds.
Now, supervisor will allow us to start all the workers we want based on its configuration file; and we need that both the NGINX and supervisor config files to match. For our Travis testing we are creating 3 workers: 21174 for master and 21175-6 as a regular workers.
If you are using NGINX via conda, you are going to need to create the NGINX folder within the environment; thus run:
mkdir -p ${CONDA_PREFIX}/var/run/nginx/Note that the shipped nginx version from conda, does not contain the mod_zip module: https://github.com/evanmiller/mod_zip
This leads to unexpected behaviour when generating a download link for anonymous artefact sharing, i.e. Qiita returns a flat file listing artifact filepaths instead of generating a ZIP archive that contains those files. You need to compile nginx with the additional mod_zip module yourself. (I've invested multiple hours to realize that the configure routine does not properly link shared libraries to the nginx binary. Try adding --with-ld-opt=" -Wl,-rpath,/home/foo/lib " to the ./auto/configure call.)
Start postgres (instructions vary depending on operating system and install method).
Next, start redis server (the command may differ depending on your operating system and install location):
redis-server --port 7777Start the qiita server:
# this builds documentation before starting the server
# alternatively: qiita pet webserver --no-build-docs start
qiita pet webserver startIf all the above commands executed correctly, you should be able to access Qiita by going in your browser to https://localhost:21174 if you are not using NGINX, or https://localhost:8383 if you are using NGINX, to login use test@foo.bar and password as the credentials. (Login as admin@foo.bar with password to see admin functionality. In the future, we will have a single user mode that will allow you to use a local Qiita server without logging in. You can track progress on this on issue #920.)
This usually happens after an incomplete run of the qiita-env setup procedure. Drop the postgres table named qiita_test and retry setting up qiita-env as per instructions above:
$ psql
DROP DATABASE qiita_test;\q
# now re-run qiita-env make --no-load-ontologiesIf you get a traceback similar to this one when starting up Qiita
File "/home/jorge/code/qiita/scripts/qiita-env", line 71, in make
make_environment(load_ontologies, download_reference, add_demo_user)
File "/home/jorge/code/qiita/qiita_db/sql_connection.py", line 120, in __init__
self._open_connection()
File "/home/jorge/code/qiita/qiita_db/sql_connection.py", line 155, in _open_connection
raise RuntimeError("Cannot connect to database: %s" % str(e))
RuntimeError: Cannot connect to database: fe_sendauth: no password suppliedit can be solved by setting a password for the database (replace postgres with the actual name of the database qiita is configured to use):
$ psql postgres
ALTER USER postgres PASSWORD 'supersecurepassword';
\q
It might be necessary to restart postgresql: sudo service postgresql restart.
Furthermore, the pg_hba.conf file can be modified to change authentication type for local users to trust (rather than, e.g., md5) but we haven't tested this solution.
Error: You need to install postgresql-server-dev-X.Y for building a server-side extension or libpq-dev for building a client-side application.
Run the following. Note that for older ubuntu versions (< 14), these commands may install an older version of postgres (< 9.3) which may cause trouble. Ensure you're downloading and installing postgresql 9.3 via a different apt repository as per instructions here.
sudo apt-get update
sudo apt-get install postgresql
sudo apt-get install postgresql-contrib
sudo apt-get install libpq-devMissing dependency. Run the following and then re-run whatever command failed earlier:
sudo apt-get install -y libffi-devfrom PyQt4 import QtCore, QtGui ImportError: libSM.so.6: cannot open shared object file: No such file or directory
sudo apt-get install -y python-qt4ERROR: could not open extension control file "/usr/share/postgresql/9.3/extension/uuid-ossp.control": No such file or directory
sudo apt-get install postgresql-contrib
# or: sudo apt-get install postgresql-contrib-9.3 depending on your OS and apt repository versionsM1 and M2 macs have a new feature where homebrew is not installed to the path usr/local/bin like Intel Macs are, but to opt/homebrew/bin. This is because of reasons including security concerns with the old path, potential conflicts with installing to /usr/local/bin, and the fact that other package managers have been using /opt/<manager_name> for a while now. To fix this, ensure that homebrew libraries are being searched for in the opt/homebrew/lib path.
Please note that the following notes are related to dependencies that Qiita does not maintain. As such, we strongly suggest you consult their official documentation to resolve issues. We cannot guarantee the accuracy of the suggestions below.
If running on OS X you should make sure that the Xcode and the Xcode command line tools are installed.
If you are using Postgres.app 9.3 on OSX, a database user will be created with your system username. If you want to use this user account, change the USER and ADMIN_USER settings to your username under the [postgres] section of your Qiita config file.
If you are getting an error message running conda create, complaining about missing packages, then you might have to locate the appropriate conda channels and re-run conda create with the --channel flag:
For example, if libgfortran is missing:
# Install anaconda-client to search repositories
conda install anaconda-client
# Now search for missing package
anaconda search -t conda libgfortran
Using Anaconda Cloud api site https://api.anaconda.org
Run 'anaconda show <USER/PACKAGE>' to get more details:
Packages:
Name | Version | Package Types | Platforms
------------------------- | ------ | --------------- | ---------------
OpenMDAO/libgfortran | 4.8.3 | conda | linux-32, osx-64
aetrial/libgfortran | | conda | linux-64
....etc....
Install the appropriate channel name that corresponds to your platform. For example, for Mac OS X 64-bit this would be:
conda install --channel https://conda.anaconda.org/OpenMDAO libgfortran
Now you can re-run your conda create command:
conda create [previous parameters go here] --channel OpenMDAO/libgfortran
As a general rule of thumb you will want to have an updated version of Python 3.6.
H5PY is known to cause a few problems, however their installation instructions are a great resource to troubleshoot your system in case any of the steps above fail.
In the event that you get _tkinter.TclError: no display name and no $DISPLAY environment variable error while trying to generate figures that rely on matplotlib, you should create a matplotlib rc file. This configuration file should have backend : agg. For more information you should visit the matplotlib configuration and troubleshooting page.
Qiita comes with a set of certs used for continuous integration (CI) tests. These certs are located in qiita_core/support_files/ and are not the certs used in production Qiita; they are for development use ONLY. When installing Qiita for development purposes you may wish to generate a set of certs and keys for your own use. dd
openssl req -x509 -sha256 -days 356 -nodes -newkey rsa:2048 -subj "/CN=localhost/C=US/L=San Diego" -keyout ci_rootca.key -out ci_rootca.crt
openssl genrsa -out ci_server.key 2048
[ req ]
default_bits = 2048
prompt = no
default_md = sha256
req_extensions = req_ext
distinguished_name = dn
[ dn ]
C = US
ST = California
L = San Diego
O = UCSD
OU = Knight Lab
CN = localhost
[ req_ext ]
subjectAltName = @alt_names
[ alt_names ]
DNS.1 = localhost
IP.1 = 127.0.0.1
openssl req -new -key ci_server.key -out ci_server.csr -config csr.conf
authorityKeyIdentifier=keyid,issuer
basicConstraints=CA:FALSE
keyUsage = digitalSignature, nonRepudiation, keyEncipherment, dataEncipherment
subjectAltName = @alt_names
[alt_names]
DNS.1 = localhost
openssl x509 -req -in ci_server.csr -CA ci_rootca.crt -CAkey ci_rootca.key -CAcreateserial -out ci_server.crt -days 365 -sha256 -extfile cert.conf
The contents of server.crt can be appended to certifi package's CA cache after which the CA cert won't need to be passed to QiitaClient objects and the like.
import certifi
certifi.where()
'/Users/qiita_user/miniconda3/lib/python3.9/site-packages/certifi/cacert.pem'
cat ci_rootca.crt >> '/Users/qiita_user/miniconda3/lib/python3.9/site-packages/certifi/cacert.pem'