-
Notifications
You must be signed in to change notification settings - Fork 317
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
Changed to allow for sub-path in url #8
Conversation
Like it. |
Close as stale. |
I think http://rack.rubyforge.org/doc/files/SPEC.html I am using Torquebox to deploy alot of little Rack apps. I was going to try to deploy geminabox, but since I would expect it to sit on some relative context like |
Actually, I think it's |
Hi, I'd love to get this kind of setup supported, but I don't use anything like your setup, so I couldn't verify the behaviour [1]. I'd welcome a patch for this. [1] Also, when it's not my itch, I don't tend to do my best scratching ;) |
Ran into the same issue deploying on passenger/nginx. The symbolic link solution did not work. http://www.modrails.com/documentation/Users%20guide%20Nginx.html#deploying_rack_to_sub_uri |
Looks like a popular request, can someone with a vested interest update @chrischillibean's patch? |
This adds support to allow hosting within an existing site: http://example.com/geminabox/ Based on the work on issue #8 by chrischillibean
Resolved in #37. |
Added a bit of extra knowledge in so that the urls are adjusted to have the full original path in, rather than assuming its hosted in /