embedding jbrowse in django site

[LeoWelter]

Hi all,
We're embedding jbrowse in a django based site, but I have some issues during development and also during production.
I try to embed jbrowse in a bootstrap4 tab in a page. Goal is to show some bam alignments on the genome (although I'm now stuck at even displaying the annotation)

When I try to load a track or the reference sequence I'm getting an error :Error: HTTP 200 (OK) when fetching /static/jbrowse/assembly/HXB2.fasta bytes 0-15871 (should be 206 for range requests). It works when I add the track through the interface, but the range reques still does not work

I guess the django development server cannot serve range requests. I tried to serve the files separately using npx serve, but then I get cors errors.

Does anyone have an example of a working development /production django environment with an embedded jbrowse section?

Best Leo

[cmdcolin]

Hi there, good question. The range requests are quite important for a lot of jbrowse features (accessing indexed file formats)

You could try using npx serve -C

Just a brief output of npx serve --help

 npx serve --help

  serve - Static file serving and directory listing

  USAGE

    $ serve --help
    $ serve --version
    $ serve folder_name
    $ serve [-l listen_uri [-l ...]] [directory]

    By default, serve will listen on 0.0.0.0:3000 and serve the
    current working directory on that address.

    Specifying a single --listen argument will overwrite the default, not supplement it.

  OPTIONS

    --help                              Shows this help message

    -v, --version                       Displays the current version of serve

    -l, --listen listen_uri             Specify a URI endpoint on which to listen (see below) -
                                        more than one may be specified to listen in multiple places

    -p                                  Specify custom port

    -d, --debug                         Show debugging information

    -s, --single                        Rewrite all not-found requests to `index.html`

    -c, --config                        Specify custom path to `serve.json`

    -C, --cors                          Enable CORS, sets `Access-Control-Allow-Origin` to `*`

    -n, --no-clipboard                  Do not copy the local address to the clipboard

    -u, --no-compression                Do not compress files

    --no-etag                           Send `Last-Modified` header instead of `ETag`

    -S, --symlinks                      Resolve symlinks instead of showing 404 errors

    --ssl-cert                          Optional path to an SSL/TLS certificate to serve with HTTPS

    --ssl-key                           Optional path to the SSL/TLS certificate's private key

    --ssl-pass                          Optional path to the SSL/TLS certificate's passphrase

    --no-port-switching                 Do not open a port other than the one specified when it's taken.

  ENDPOINTS

    Listen endpoints (specified by the --listen or -l options above) instruct serve
    to listen on one or more interfaces/ports, UNIX domain sockets, or Windows named pipes.

    For TCP ports on hostname "localhost":

      $ serve -l 1234

    For TCP (traditional host/port) endpoints:

      $ serve -l tcp://hostname:1234

    For UNIX domain socket endpoints:

      $ serve -l unix:/path/to/socket.sock

    For Windows named pipe endpoints:

      $ serve -l pipe:\\.\pipe\PipeName

It may help to consider what the final deployment will be also