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
RACK_BASE_URI and delegating to Sinatra/Rack #1532
Comments
Could you try |
Oh, asset_path :, 'my_data'
# => /my_app/my_data?1388045670 Thank you. So that kind-of solves one of my problems. (It also appends the timestamp, without the option to switch it off; since my asset is static and unlikely to change, and allowing caching would make sense, a pure The fact remains that |
I will fix and document it soon. I assume you are aware of As for |
Thank you, the patch makes sense.
Actually, I was not, thank you for that as well. I am a newcomer to Padrino, don't know all the ins and outs yet. Coincidentally, is there a central list of all the options? I find Padrino nice to work with, but I struggle with documentation.
I'd rather say that |
Yeah, there should be a list. The closest thing to it is |
I am proxying my Padrino application from http://example.com/my_app/ to http://example.com:5000/:
and over there, I'm running Padrino in Puma, with
RACK_BASE_URI
set to/my_app
.If I'm using Padrino's new URL generation, all is fine (assuming
get :test
is defined):But in some circumstances, things are left to Sinatra or Rack, neither of which knows anything about
RACK_BASE_URI
:(I wanted to get the URL to files within
public
which were not understylesheets
,javascripts
orimages
, and thus not reachable byasset_path
. I made a workaround with#{ url :index }/my_data
, but it is hardly elegant.)Another place I found (as much as I could see) is
store_location!
from padrino-admin: it just usesSCRIPT_URI
, which will be the local/protected
, and not/my_app/protected
, which makesredirect_back_or_default
hit the wrong location. (Maybe this should be a new issue?)Anyway, if I am doing something wrong, I shall appreciate the feedback, since I could not find much documentation on this.
The text was updated successfully, but these errors were encountered: