Add the ability to mount Jingo on a URL path

[claudioc]

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

[creynold]

I can't think of a way of doing this other than prefixing all URLs in the templates with a #{mountpath} and defining this mountpath in the config file. This seems rather ugly. Is there some way to prefix all urls in Jade?

[claudioc]

I see two solutions:

1. Verify if passing the mount point to express.static (in lib/app.js) would solve this issue right away (see http://expressjs.com/en/starter/static-files.html)
2. Create a cssAsset and jsAsset mixins which will create a link or a script jade tag taking care of the mountpath.

So, instead of

    link(rel="stylesheet", href="/css/ionicons.min.css")
    link(rel="stylesheet", href="/css/shCoreDefault.css")

one could write

    cssAsset("onicons.min.css")
    cssAsset("shCoreDefault.css")

[creynold]

Solution 1 wouldn't work, unfortunately, (at least as-is) because the assets linked on the layout.jade file point to for example href="/css/style.css". This root-relative url still needs to be prepended with the application mount-point.

I'm working on solution 2 as we speak.

[claudioc]

I see.

What about asset('onicons.min', 'css'), or even sniffing the extension? (cssAsset is a bit lame :P)

[creynold]

Yeah, I agree. I can change that

[creynold]

Ok I pushed a mixin called asset which sniffs the extension and renders the appropriate tag.

[claudioc]

Released with 1.6.0