rack

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 7 years ago . I'm trying to decide between Unicorn and Phusion Passenger Standalone (formerly Phusion Passenger Lite). I want to host multiple apps on my server. I have nginx running and listening to port 80. I need a webapp server that I can proxy

I have a Rails 4 sample project (Blog) and I have created a simple middleware called 'request_timer' in config/initializers/request_timer.rb #config/initializers/request_timer.rb class RequestTimer def initialize(app) @app = app end def call(env) start_time = Time.now status, headers, response = @app.call(env) stop_time = Time.now [status, headers, response.body] end end and I have added my middleware in config/application.rb in two ways 1 ) Adding as a constant #config/application.rb module Blog class Application < Rails::Application config.middleware.use RequestTimer end end this way when I

I have an app on heroku, running on Puma: workers 2 threads_count 3 pool 5 It looks like some requests get stuck in the middleware, and it makes the app very slow (VERY!). I have seen other people threads about this problem but no solution so far. Please let me know if you have any hint. ! ! I work for Heroku support and Middleware/Rack/ActiveRecord::QueryCache#call is a commonly reported as a problem by New Relic. Unfortunately, it's usually a red herring as each time the source of the problem lies elsewhere. QueryCache is where Rails first tries to check out a connection for use, so any

My setup: Rails 3.0.9, Ruby 1.9.2 I am working on my first middleware app and it seems like all of the examples deal with modify the response. I need to examine and modify the request headers in particular, delete some offending headers that cause a bug in Rack 1.2.3 to choke. Here's the typical hello world Rack app. my_middleware.rb class MyMiddleware def initialize(app) @app = app end def call(env) @status, @headers, @response = @app.call(env) [@status, @headers, @response] end end Does anyone have an example that deals with the request headrers and intercepting them before Rack gets hold of

I'm trying to use a Sinatra app as middleware in my Rails app. I've tested a basic Sinatra app in the /lib folder of the Rails app, use d the middleware and set a route. That worked fine. What I want to be able to do is extract the Sinatra app and include it as a gem. That way I can run the Sinatra app independently, or use it in multiple Rails apps. Sinatra App # myrackapp/lib/myrackapp.rb module Myrackapp class Application < Sinatra::Base set :root, File.dirname(__FILE__) get "/" do "Rack Home" end get '/rackroute' do "Hello, Rack Page" end end end Myrackapp also has a gemspec – nothing