There are use cases where Jingo lives behind a reverse proxy for a single path, like in mywebsite.com/wiki and wiki is proxy_passed by nginx to jingo. At the moment it seems impossible (as for the example goes) to instruct jingo to use /wiki as its "base" so that its assets are relative to that one (like /wiki/style.css).

It would be probably possible to hack something similar to what WordPress does with its WP_SITEURL configuration directive