-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the ability to mount Jingo on a URL path #124
Comments
I can't think of a way of doing this other than prefixing all URLs in the templates with a |
I see two solutions:
So, instead of
one could write
|
Solution 1 wouldn't work, unfortunately, (at least as-is) because the assets linked on the I'm working on solution 2 as we speak. |
I see. What about |
Yeah, I agree. I can change that |
Ok I pushed a mixin called |
Released with 1.6.0 |
There are use cases where Jingo lives behind a reverse proxy for a single path, like in
mywebsite.com/wiki
andwiki
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
The text was updated successfully, but these errors were encountered: