Tutorial
For details consult instalation page.
docker run -i -t -v /home/yourvolume:/var/www/html/EvoMining/exchage -p 80:80 nselem/newevomining:latest /bin/bash
nselem/newevomining:latest is the image being run.
docker run is the command to run the image. Docker run has the following modifiers:
| -i, --interactive | Keep STDIN open even if not attached |
| -t, --tty | Allocate a pseudo-TTY (a linux terminal) |
| -v, --volume value | Bind mount a volume (default []). (Allows to share data and to keep results after the ephimer container dies) |
| -p, --publish value | Publish a container's port(s) to the host (default []) |
Thats why on the modifier -v
-v /home/yourvolume:/var/www/html/EvoMining/exchage
where /home/yourvolume should be your local volume, the place where your data will be stored.
If you want to use your own databases this is the place where you should store them,.
-p 80:80
/bin/bash
perl startevomining -g mygenomes -r myRastIds
| Argument | Default | Description |
| --genome_db,g | Default los17 | Genome files from RAST (*.faa, *.txt) Each file should be named JobId.faa or JobId.txt same JobId as in RAST. Also JobId.faa.evo files can be used to save time. |
| --rast_ids,r | Required when genome is used (No Default) | RAST ids tab-separated table Columns: Job id\tGenome id\tOrganism name |
| --natural_db,n | Default MiBIG_DB.faa | Natural products DB that will be used to detect expansions |
| --central_db,n | Default ALL_curado.fasta | Central pathways DB. All enzymes that are BBH with enzymes on this data base will be considered to be involved on central pathway and not on expansions |
If you are running EvoMining on your local machine.
http://localhos/html/evoMining/indexORIG.html
or, if you are running EvoMining on a remote machine.
http://yourip/html/evoMining/indexORIG.html
and follow the steps.
