Install your own instance

Latest available version: 1.2.0



Install in 1 step:

As root:

pip3 install dgenies

Or as simple user:

pip3 install dgenies --user

Alternatively, you can install it manually:

git clone
cd dgenies
pip3 install -r requirements.txt
python3 install


Standalone mode

pip3 install dgenies --upgrade

Add --user flag if you have not root access.

Webserver mode

dgenies clear -c
pip3 install dgenies --upgrade

Then, you need to restart your webserver.


D-Genies requires python >= 3.5 to run.

We use minimap2 for mapping. A binary of minimap2 is shipped with the program. Alternatively, you can install your own from their repository.

Some python modules are required (will be automatically installed by the commands above):


Additional modules for webserver mode:


And if you use a cluster (webserver mode):


In webserver mode, you must install mysqlclient python module (will not be installed automatically) if you use mysql as RDBM.


We provide an installer to install D-Genies. You can download it here.

All requirements are present inside the package, so you don't have to do anything else.

System requirements

You need Windows 7 or newer, 64 bits architecture.

How to start

You can launch DGenies in standalone mode or in webserver mode. You can use standalone mode if you launch it locally and only one user launch jobs at once. If you are several users to use it simultaneously or if you run it on a server, you must run it in webserver mode.

Standalone mode

Unix: start with the command below:

dgenies run

Optional arguments:

-p <port> run in a specified port (default: 5000) --no-browser don't start the browser automatically

Windows: just click on the launcher in the desktop or into the install folder.

Webserver mode

Note: this mode is only available for Unix systems and will NOT work on MS Windows.

Flask webserver (which is used in standalone mode) is not recommended in production servers. So, we recommend using the WSGY module of Apache (or µWSGI + nginx, not documented here).

Once dgenies is installed, you just need to use the /var/www/dgenies.wsgi file into your apache virtualhost file.

Here is an example of configuration file for apache:

<VirtualHost *>
    ServerName <url>

    WSGIDaemonProcess dgenies user=<user> group=<group> threads=8
    WSGIScriptAlias / /var/www/dgenies/dgenies.wsgi

    <Directory /var/www/dgenies>
        WSGIProcessGroup dgenies
        WSGIApplicationGroup %{GLOBAL}
        Order deny,allow
        Allow from all

With: <url>: the URL of your instance <user>: the user who launch the server <group>: the group who launch the server

Debug method

For debug or for development only, you can launch dgenies through flask in webserver mode:

dgenies run -m webserver

Optional parameters:

-d run in debug mode -o <IP> specify the host into run the application (default:, set for distant access) -p <port> run in a specified port (default: 5000) --no-crons don't run the crons automatically --no-browser don't start the browser automatically (always true if -d option is given)

Running with a cluster

If you want to run jobs on a cluster, some configuration is required. We only support SLURM and SGE schedulers. But please note that only SLURM scheduler has been fully tested.

Note: submitting jobs on a cluster is only available for webserver mode.

Jobs are submitted throw the DRMAA library. So you need it for your scheduler. Please see configuration below to define path to this library.

Also, scripts for preparing data must be moved in a location accessible by all nodes of your cluster. You must move them in a same folder and set the full path to script (full path on the nodes of the cluster) in the configuration file (see below).

To get these scripts, follow the commands below:

curl >
python -d <dir>

With <dir>: the folder into save the scripts (must be accessible by cluster nodes).


Changing the default configuration is not required for standalone mode, but you can want to custom some parts of the program.

Configuration file location:
* /etc/dgenies/ if installed with root access
* ~/.dgenies/ else
* file of the install folder

The file is divided in 9 parts described below.

To change this file, please copy it into (at the same location) to avoid erase of the file on upgrades.


Main parameters are stored into this section:

  • config_dir: where configuration file will be stored.
  • upload_folder: where uploaded files will be stored.
  • data_folder: where data files will be stored (PAF files and other files used for the dotplot).
  • threads_local: number of threads to use for local jobs.
  • web_url: public URL of your website.
  • max_upload_size: max size allowed for query and target file (-1 to avoid the limit) - size uncompressed.
  • max_upload_size_ava: max size allowed for target file for all-vs-all mode (only target given, -1 to avoid the limit) - size uncompressed.
  • max_upload_file_size: max size of the uploaded size (real size of the file, compressed or not, -1 to avoid the limit).

For webserver mode only (ignored in standalone mode):

  • batch_system_type: local for run all jobs locally, sge or slurm to use a cluster scheduler.


Some parameters for debug:

  • enable: True to enable debug
  • log_dir: folder into store debug logs


This section concerns only the webserver mode with batch_system_type not set to local.

  • drmaa_lib_path: absolute path to the drmaa library. Required as we use the DRMAA library to submit jobs to the cluster.
  • native_specs: how to set memory, time and number of CPU on the cluster (should be kept as default).

By default, small jobs are still launched locally even if batch_system_type is not set to local, and if not too much of these jobs are running or waiting. This limit can be customized:

  • max_run_local: max number of jobs running locally (if this number is reached, future jobs will be submitted to the cluster regardless of their size). Set to 0 to run all jobs on the cluster.
  • max_wait_local; max number of jobs waiting for a local run (if this number is reached, future jobs will be submitted to the cluster regardless of their size). Set to 0 to run all jobs on the cluster.

You can also customize the size from which jobs are submitted on the cluster. If only one of these limit is reached, the job is submitted on the cluster.

  • min_query_size: minimum size for the query (uncompressed).
  • min_size_target: minimum size for the target (uncompressed).

Other parameters:

  • prepare_script: absolute path to the script downloaded in the section above.
  • python3_exec: path to python3 executable on the cluster.
  • memory: max memory to reserve on the cluster.
  • memory_ava: max memory to reserve on the cluster un all-vs-all mode (should be higher than memory).
  • threads: number of threads for launching jobs on the cluster (must be a divider of the memory).


This section concerns only the webserver mode.

In webserver mode, we use a database to store jobs.

  • type: sqlite or mysql. We recommend mysql for better performances.
  • url: path to the sqlite file, or url to the mysql server (localhost if the mysql server is on the same machine).

If type is mysql, some other parameters must be filled:

  • port: port to connect to mysql (3306 as default).
  • db: name of the database.
  • user: username to connect to the database.
  • password: the associated password.


This section concerns only the webserver mode.

At the end of the job, a mail is send to the user to advise him of the end of the job.

  • status: mail to use for status mail.
  • reply: mail to use as reply to.
  • org: name of the organisation who send the mail.
  • send_mail_status: True to send mail status, False else. Should be True in production.


This section concerns only the webserver mode.

We use crons to launch the local scheduler who start jobs, and some script that clean old jobs.

  • clean_time: time at which we launch the clean job (example: 1h00)
  • clean_freq: frequency of the clean job execution


This section concerns only the webserver mode.

Several parameters for jobs:

  • run_local: max number of concurrent jobs launched locally.
  • data_prepare: max number of data prepare jobs launched locally.
  • max_concurrent_dl: max number of concurrent upload of files allowed.


Here, you can fill example data. At least target is required to enable example data.

Fill for target and query the absolute local path of the file. This path will not be shown to the client. Only the file name will be shown.

If at least target is filled, a button "Load example" will be shown in the run form. Click on it will load example data in the form.


Set enable_logging_runs to True will enable storage of analytics data. It stores for each job creation date, user mail, size of query and target, and batch type.

Customize your installation

You can make easily make some changes to the application, described below. To do so, you must first clone the D-Genies repository (except if changes can be done in the current installation, see below):

git clone

The created folder is named the D-Genies repository in the text below.

Then, you make changes described below. When done, you can easily install the cusomized version with this command:

pip install .

Add the --upgrade flag if you already have D-Genies installed.

Add or change alignment tools

D-Genies uses minimap2 as default aligner, but you can add other tools, or replace minimap2 by another tool. You can also change minimap2 executable path.

If your tool needs a parser (see below), you must customize the installation (see above). For other changes, you can make them on your current installation.

Tools definition YAML file:
* /etc/dgenies/tools.yaml if installed with root access
* ~/.dgenies/tools.yaml else
* tools.yaml file of the install folder

To change this file, please copy it into tools.yaml.local (at the same location) to avoid to erase the file on upgrades.

Note: you can also edit the tools.yaml file of the D-Genies repository, which will be installed then (if you customize the installation). Edit it without renaming it.

For each tool, you can or must define several properties described bellow.

Executable path


Always set tool binary path in the exec property. If it differs for cluster execution, set it in the exec_cluster property.

Command line skeleton


The command line skeleton defines how to launch the program, in the command_line property. The skeleton must include the following tags:

  • {exe}: will be replaced by the executable path
  • {target}: will be replaced by the target fasta file
  • {query}: will be replaced by the query fasta file
  • {out}: will be replaced by the output file

If the tool can be multithreaded, add the {threads} tag which will be replaced by the number of threads to use.

If your program is able to use all-vs-all mode (target versus itself), define the same skeleton in the all_vs_all property. All tag described hereover must be set except the {query} tag.



Defines how much threads to use for this tool. Set it in the threads property for local executions, and the threads_cluster property for cluster execution (if different from the local one).

Max memory


If the tool requires less memory than defined in the configuration file, you can add the max_memory property. The unit is Gb.



If the tool does not output PAF format, you must define a function in the src/dgenies/lib/ file of the D-Genies repository. This function get the input file as first parameter and outputs a valid PAF file (output file, second parameter). You must reference the function name in the parser property.

Split before

Optional. Default: False

For some tools (like minimap2), splitting the query on 10 Mb blocks improves performances (blocks are merged after mapping). To enable this for the tool, set the split_before property to True.



Define a message to show aside the tool name in the run form. Set it in the help property.


Optional. Default: random.

Define in which order we show tools in the run form. Set it in the order property.

Add new formats

In Plot alignment mode in run form (see here), we propose by default only PAF and MAF formats. It's easy to add new formats.

Just define 2 functions:

  • Add the first one in the src/dgenies/lib/ file of the D-Genies repository. It takes only one argument: the input file. It checks if the file format is correct and returns True in this case, else it returns False. The function name must be the same as the expected input file extension.
  • Add the second one in the src/dgenies/lib/ file of the D-Genies repository. It takes two arguments: the input and the output file. It convert the input file into a valid PAF file. The function name must be same as the previous one.


The dgenies command can be used to do some maintenance staff.

Clear all jobs:

dgenies clear -j [--max-age <age>]

--max-age (opt): set the max age of jobs to delete (default: 0, for all)

Clear all log:

dgenies clear -l

Clear crons (webserver mode):

dgenies clear -c

Display message on run form:

You can display a message at the top of the run form. It can be used to add extra informations for user, or for prevent him for problem or for a maintenance on your instance.

dgenies inforun -m "message to display" -t [warn, critical, info, success]

-m <message>: message to display. Html allowed.
-t <type>: type of message: warn (orange background), critical (red background), info (blue background) or success (green background).

Remove the message by:

dgenies inforun -c

Note: gallery is only available in webserver mode.

To add a job to the gallery, copy illustrating picture file into the gallery folder inside the data folder (~/.dgenies/data/gallery as default, create it if not exists). Then use the dgenies command:

dgenies gallery add -i <id_job> -n <name> -q <query_name> -t <target_name> -p <pict_filename>

With: id_job: the name of the job name: name of the job to show in the gallery query_name: name of the query target_name: name of the target pict_filename: filename added in the gallery folder (without path)

You can also delete an item from the gallery:

dgenies gallery del -i <id_job>


dgenies gallery del -n <name>

With id_job and name as described above. You can add the --remove-pict option to remove the picture file from the gallery folder.

Note: first item of the gallery will be shown on home page.