From cb3c5b7a5e72290b35cae9b5b45118fe20ea85b6 Mon Sep 17 00:00:00 2001 From: Martin Cech Date: Fri, 2 Aug 2019 09:36:37 -0400 Subject: [PATCH] mention IGB in the docs --- doc/source/admin/nginx.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/admin/nginx.md b/doc/source/admin/nginx.md index f73f98a9f67..33763b63095 100644 --- a/doc/source/admin/nginx.md +++ b/doc/source/admin/nginx.md @@ -242,9 +242,9 @@ previous section: Galaxy sends files (e.g. dataset downloads) by opening the file and streaming it in chunks through the proxy server. However, this ties up the Galaxy process, which can impact the performance of other operations (see [Production Server -Configuration](production.md) for a more in-depth explanation). +Configuration](production.md) for a more in-depth explanation). -Nginx can assume this task instead and, as an added benefit, speed up downloads. In addition, both the IGV genome browser and JBrowse tool (run within Galaxy) require support for the HTTP *Range* header, and this is only available if the proxy serves datasets. +Nginx can assume this task instead and, as an added benefit, speed up downloads. In addition, the Integrative Genomics Viewer (IGV), the Integrated Genome Browser (IGB), and the JBrowse tool (run within Galaxy) require support for the HTTP *Range* header, and this is only available if the proxy serves datasets. This is accomplished through the use of the special `X-Accel-Redirect` header. Dataset security is maintained in this configuration because nginx will still check with Galaxy to ensure that the requesting user has permission to access the dataset before sending it. To enable it, add the following to your Galaxy's `server {}` block: