about summary refs log tree commit diff
path: root/test/python
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-11-06 17:33:04 +0000
committerPjotr <wrk@bosa.lan>2026-11-06 17:33:04 +0000
commit5c21b0513a26cce220ddfae560a1290e39522106 (patch)
tree12a485a02b02b93e6a0cb33c40860cfafc9d3c55 /test/python
parentc39dd5440e29b7d6abcc602009c863a2c11ae1f7 (diff)
downloadgenenetwork4-5c21b0513a26cce220ddfae560a1290e39522106.tar.gz
docs: publish genenetwork4 under a path prefix with nginx
The deployment being set up is https://vesuvio.pu.ac.uk/gn4 proxying to
a loopback port, with no gn-auth yet. Two things there are not obvious
and neither is discoverable from the README's /get-test-token section:
every link the API emits is root-relative, so under /gn4 they resolve
outside the mount point; and /compute/* runs for minutes in a single
request, so nginx's one-minute default read timeout cuts it off
mid-computation.

The link rewriting is the delicate part -- the server's serde output is
compact ("href":"/"), not the pretty-printed shape the README examples
show, so a filter written from those examples silently does nothing.
Both spellings of all four affected keys (href, next, spec_url, type)
are in the config, and the envelope's "next":[ array is deliberately
left alone.

* docs/nginx.md: new file. Server environment, the nginx block, what the
prefix does to links and the three ways to handle it, stub-minted
tokens instead of gn-auth, and how to check the result.
* README.md (Behind nginx or in a container): point at it.
Diffstat (limited to 'test/python')
0 files changed, 0 insertions, 0 deletions