rack

I'm in the process of refactoring some logic built into a Rails application into middleware, and one annoyance I've run into is a seeming lack of convention for where to put them. Currently I've settled on app/middleware but I could just as easily move it to vendor/middleware or maybe vendor/plugins/middleware ... The biggest problem is having to require the individual files at the top of config/environment.rb require "app/middleware/system_message" require "app/middleware/rack_backstage" or else I get uninitialized constant errors on the config.middleware.use lines. That could get messy very

I would like to mount a sinatra application in my rails app. But I would like this one to share the same layout. The iframe could work but do you have any other idea ? Thanks You basically need to do two things: You need to tell the Rails router that a certain URL path is to be handled by another Rack app (in your case a Sinata app). This can be done by adding this to your routes.rb: match "/sinatra" => MySinatraApp, :anchor => false Having done that, you can create your app like so: class MySinatraApp < Sinatra::Base get "/" do "Hello Sinatra World" end end The second step now is to tell your

I wanted to implement CORS in my rails application, so I googled rack-cors gem for it. And I did everything as was said in README, that is updated Gemfile accordingly and updated application.rb like this: module YourApp class Application < Rails::Application # ... config.middleware.use Rack::Cors do allow do origins '*' resource '*', :headers => :any, :methods => [:get, :post, :options] end end end end But it didn't work. No matter what I did, in the browser console I kept getting message: XMLHttpRequest cannot load https://somewebsite.com. Origin http://0.0.0.0:3000 is not allowed by Access

I understand there are a lot of questions that answer this. I'm familiar with .htaccess and nginx.conf methods, but I do not have access to such traditional configuration methods on heroku. Simone Carletti gave this answer that leverages Rails 2.x Metals, but I'm using Rails 3 and this isn't compatible. Redirect non-www requests to www urls in Rails Please note: I'm not looking for a simple before_filter in my ApplicationController. I'd like to accomplish a rewrite similar to Simone's. I believe this is job for the webserver or middleware like Rack at the very least, so I'd like to leave this

I have a rule in my routes.rb: constraints AssetRestrictor do match '*seopath' => SeoDispatcher end Then in lib/seo_dispatcher.rb, I have this: class SeoDispatcher AD_KEY = "action_dispatch.request.path_parameters" def self.call(env) seopath = env[AD_KEY][:seopath] if seopath params = seopath.split('/') # get array of path components env[AD_KEY][:id] = params.last # the real page name is the last element env[AD_KEY][:category] = params.first if params.length > 1 end Rails.logger.debug "routing to show #{env[AD_KEY]}" PagesController.action(:show).call(env) # TODO error handling for invalid

I have a Rack application that looks like this: class Foo def initialize(app) @app = app end def call(env) env["hello"] = "world" @app.call(env) end end After hooking my Rack application into Rails, how do I get access to env["hello"] from within Rails? Update : Thanks to Gaius for the answer. Rack and Rails let you store things for the duration of the request, or the duration of the session: # in middleware def call(env) Rack::Request.new(env)["foo"] = "bar" # sticks around for one request env["rack.session"] ||= {} env["rack.session"]["hello"] = "world" # sticks around for duration of

I have been using Sinatra for sometime now and I would like to add some realtime features to my web-app by pushing the data via websockets. I have successfully used the gem 'em-websocket' on its own, but have not been able to write one ruby file that has a sinatra web server AND a web-socket server. I've tried spinning the run! or start! methods off in separate threads with no success. Has anyone gotten this to work? I want to have them in the same file as I can then share variables between the two servers. Thanks! Konstantin Haase Did not try it, but should not be too hard: require 'em