|
1 | 1 | # LOLAweb |
| 2 | + |
| 3 | +[](https://github.com/databio/LOLAweb/actions/workflows/build.yml) |
| 4 | + |
2 | 5 | LOLAweb is a web server and interactive results viewer for enrichment of overlap between a query region set (a bed file) and a database of region sets. It provides an interactive result explorer to visualize the highest ranked enrichments from the database. You can access the web server at <http://lolaweb.databio.org>. |
3 | 6 |
|
4 | | -This repository contains two components: 1) the shiny [app source code](apps/LOLAweb/) and 2) [Docker implementation](docker/) for LOLAweb. |
| 7 | +This repository contain the shiny [app source code](apps/LOLAweb/) and Docker implementation for LOLAweb. |
5 | 8 |
|
6 | 9 | ## Shiny app |
7 | 10 |
|
8 | 11 | LOLAweb is implemented as an interactive Shiny app. You can run this app locally by following the [instructions in the appfolder](apps/LOLAweb/). |
9 | 12 |
|
10 | 13 | ## Docker |
11 | 14 |
|
12 | | -We have also produced a Dockerfile and published an image on Docker Hub (`databio/lolaweb`). Learn how to run LOLAweb locally in a docker container by reading the [instructions in the docker folder](docker/). |
| 15 | +The `ghcr.io/databio/lolaweb` container is based on the `ghcr.io/databio/shinybase` container, which you can find in its [GitHub repository](https://github.com/databio/shinyBase) or in the [GitHub Container Registry](https://github.com/databio/shinyBase/pkgs/container/shinybase). |
| 16 | + |
| 17 | +### `build` the container image yourself |
| 18 | + |
| 19 | +1. Clone this repository |
| 20 | +2. Build locally using Docker. Run this command from the same directory as the `Dockerfile`. |
| 21 | + |
| 22 | +```docker build --no-cache -t lolaweb .``` |
| 23 | + |
| 24 | + |
| 25 | +### Or `pull` the container image: |
| 26 | + |
| 27 | +```docker pull ghcr.io/databio/lolaweb``` |
| 28 | + |
| 29 | +The container image itself is hosted in the GitHub Container Registry: https://github.com/databio/LOLAweb/pkgs/container/lolaweb |
| 30 | + |
| 31 | +### Container volumes and reference data |
| 32 | + |
| 33 | +LOLAweb needs access to a few folders where it can store results or logs, or access necessary files like the database. To handle this, we've set up the app to look for two shell environment variables: |
| 34 | + |
| 35 | +* **$LWREF**, for LOLAweb reference data, which may be read-only |
| 36 | +* **$LWLOCAL**, where local results can be written. |
| 37 | + |
| 38 | +To run the LOLAweb container (locally or on a server), you need to set these environment variables (for example, in your `.bashrc` or `.profile` file. These variables will be injected into the container when it is run. |
| 39 | + |
| 40 | +For example, set these variables to two different paths if you like. Or if you keep all five subfolders together in the same path, set these variables to the same value. |
| 41 | + |
| 42 | +``` |
| 43 | +# Example locations. Set to match your environment |
| 44 | +export LWREF='/home/subdir/lola/' |
| 45 | +export LWLOCAL='/var/things/loladata/' |
| 46 | +``` |
| 47 | + |
| 48 | +LOLAweb will look at the value in `$LWREF` for the reference data. This folder should have subfolders called `databases`, `universes`, and `examples`. In each of these subfolders are another layer of subfolders for genome assemblies |
| 49 | + |
| 50 | +LOLAweb looks for `$LWLOCAL` to have two subfolders: `cache`, and `shinylogs`. This is where the app will write results and log files. If running LOLAweb on a server, be sure these directories are writeable by the Docker process. |
| 51 | + |
| 52 | +The following instructions demonstrat how to download and configure the LOLAweb data directories for a minimal example using `hg19` reference data: |
| 53 | + |
| 54 | +``` |
| 55 | +## assign env vars for data path |
| 56 | +## NOTE: must include trailing / |
| 57 | +LWLOCAL="/path/to/local/data/" |
| 58 | +LWREF="/path/to/reference/data/" |
| 59 | +
|
| 60 | +## change reference data dir |
| 61 | +cd $LWREF |
| 62 | +
|
| 63 | +## create dir for databases |
| 64 | +mkdir -p databases |
| 65 | +## create examples and universe dir |
| 66 | +## NOTE: these must include subdirs named corresponding to appropriate ref genome |
| 67 | +mkdir -p examples/hg19 |
| 68 | +mkdir -p universes/hg19 |
| 69 | +
|
| 70 | +## download example universe and user set |
| 71 | +curl http://cloud.databio.org.s3.amazonaws.com/vignettes/lola_vignette_data_150505.tgz | tar xvz |
| 72 | +
|
| 73 | +## move example universe and user set files to hg19 dir |
| 74 | +mv lola_vignette_data/activeDHS_universe.bed universes/hg19/. |
| 75 | +mv lola_vignette_data/setB_100.bed examples/hg19/. |
| 76 | +
|
| 77 | +## clean up |
| 78 | +rm -rf lola_vignette_data |
| 79 | +
|
| 80 | +## download databases |
| 81 | +curl http://cloud.databio.org.s3.amazonaws.com/regiondb/LOLACoreCaches_170206.tgz | tar xvz |
| 82 | +curl http://cloud.databio.org.s3.amazonaws.com/regiondb/LOLAExtCaches_170206.tgz | tar xvz |
| 83 | +
|
| 84 | +## move databases to appropriate spots |
| 85 | +mv scratch/ns5bc/resources/regions/LOLACore databases/Core |
| 86 | +mv scratch/ns5bc/resources/regions/LOLAExt databases/Extended |
| 87 | +
|
| 88 | +## clean up |
| 89 | +rm -rf scratch |
| 90 | +
|
| 91 | +## change ot local data dir |
| 92 | +cd $LWLOCAL |
| 93 | +
|
| 94 | +## create placeholder dirs for cache and shinylog |
| 95 | +mkdir -p cache |
| 96 | +mkdir -p shinylog |
| 97 | +``` |
| 98 | + |
| 99 | +### Run the LOLAweb container locally with reference data: |
| 100 | + |
| 101 | +``` |
| 102 | +## run the docker image |
| 103 | +## NOTE: this run command uses image pulled from ghcr.io/databio/lolaweb |
| 104 | +docker run -d \ |
| 105 | + -p 80:80 \ |
| 106 | + -e LWREF=$LWREF \ |
| 107 | + -e LWLOCAL=$LWLOCAL \ |
| 108 | + --volume ${LWLOCAL}:${LWLOCAL} \ |
| 109 | + --volume ${LWREF}:${LWREF} \ |
| 110 | + --volume ${LWLOCAL}/shinylog:/var/log/shiny-server \ |
| 111 | + ghcr.io/databio/lolaweb |
| 112 | +``` |
| 113 | + |
| 114 | +Open a browser to: |
| 115 | +``` |
| 116 | +http://localhost |
| 117 | +``` |
| 118 | + |
| 119 | +### Running a `dev` container |
| 120 | + |
| 121 | +You could also run the `dev` version of the container by pulling `ghcr.io/databio/lolaweb:dev`. This will retrieve the dev tagged image from the GitHub Container Registry. Just add `:dev` to the container name at the end of the `docker run` command above. |
| 122 | + |
| 123 | +### Running multiple LOLAweb containers simultaneously with Docker Swarm |
| 124 | + |
| 125 | +For the typical use case of an individual user, a single running container will suffice. But if you need to set up an enterprise-level LOLAweb server that can handle concurrent users, we've also made that easy by using Docker Swarm. This is how we run the main LOLAweb servers, and you could do the same thing if you want your own local implementation. Docker Swarm is a technique for running multiple instances of the same container. [Read more](swarm/README.md) about how to set up your own swarm. |
| 126 | + |
| 127 | +### Troubleshooting |
| 128 | + |
| 129 | +The LOLAweb Docker implementation includes a mechanism to write Shiny Server logs to `$LWLOCAL/shinylog`. These log files may be useful when troubleshooting problems with running LOLAweb via Docker. They include errors with R processing as well as information as to whether the Shiny Server process was killed due to resource limitations (i.e., not enough RAM allocated to Docker daemon). |
| 130 | + |
| 131 | +For additional support with the LOLAweb Docker implementation, please file a [GitHub issue](https://github.com/databio/LOLAweb/issues). |
| 132 | + |
0 commit comments