Difference between revisions of "Website:JBrowse set-up on dev.wormbase.org"
Line 1: | Line 1: | ||
These are the directions for setting up a new instance of JBrowse on dev.wormbase.org, which is where the current production version of JBrowse is hosted. | These are the directions for setting up a new instance of JBrowse on dev.wormbase.org, which is where the current production version of JBrowse is hosted. | ||
− | Get the current JBrowse release | + | ==Set up== |
+ | |||
+ | Get the [http://jbrowse.org/category/jbrowse-software-releases/ current JBrowse release], put it somewhere with a fair amount of disk space (current build is about 45GB). This directory will be JBrowse is served from, so it it will need to be made accessible to Apache when the set up is complete. The actual setup of JBrowse is quite easy; in the directory where the JBrowse release has been unzipped, do this: | ||
+ | |||
+ | ./setup.sh | ||
+ | |||
+ | without root privileges. The setup script will use local::lib to install any needed perl prerequisites as well as | ||
Get a fresh checkout of website-admin (build scripts and track configs are in there) | Get a fresh checkout of website-admin (build scripts and track configs are in there) |
Revision as of 17:09, 5 January 2015
These are the directions for setting up a new instance of JBrowse on dev.wormbase.org, which is where the current production version of JBrowse is hosted.
Set up
Get the current JBrowse release, put it somewhere with a fair amount of disk space (current build is about 45GB). This directory will be JBrowse is served from, so it it will need to be made accessible to Apache when the set up is complete. The actual setup of JBrowse is quite easy; in the directory where the JBrowse release has been unzipped, do this:
./setup.sh
without root privileges. The setup script will use local::lib to install any needed perl prerequisites as well as
Get a fresh checkout of website-admin (build scripts and track configs are in there)
Edit the build configuration file--only the top part should have to be changed unless there are new data types
Create a "multi-species" build shell script and run (best done in a screen process, and/or grab stdout and stderr to a file); it'll take about a day)
Update apache config to point at new build.