Skip to content
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

Phusion Passenger and Apache #14

Open
geneeblack opened this issue Oct 3, 2017 · 1 comment
Open

Phusion Passenger and Apache #14

geneeblack opened this issue Oct 3, 2017 · 1 comment

Comments

@geneeblack
Copy link

Attempting to use this under Passenger and Apache but it does not seem to be getting to the redirect. Any guidance on what I should look for or is this known to work/not work under these conditions? (Other Rack middleware has not had an issue but they were not doing redirects).

I have confirmed that:
config.assets.digest = true
config.assets.compile = false

assets are compiled and a manifest.yml exists in the default asset directory, I have confirmed
that entries exist for images that are not being redirected

I am not directly setting any config options for sprockets-redirect
I have not seen any logging indicating that the class was loaded/not loaded

The same configuration works great when running locally under Webrick

@geneeblack
Copy link
Author

Never mind, the reason why it doesn't work with passenger is because access to the assets directory is bypassing rails.

https://www.phusionpassenger.com/library/dev/ruby/rails_integration.html#asset-pipeline

Even though it is somewhat ambiguous when it later says it only applies to Nginx, I'm sure this is what is happening based on the symptoms and the fact that I could not find any other config items in Apache that would be interfering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant