I assume that you are going to have more than a few of these multiple-choice attributes, and would like to keep things tidy. I would recommend the store it in the database approach only if you want to modify the choices at runtime, otherwise it would quickly become a performance hit; If a model has …
I’m a little late to the party, but thought I’d post what worked for me. Essentially, I have god setup to monitor redis and resque. If they aren’t running anymore, god starts them back up. Then, I have a rake task that gets run after a capistrano deploy that quits my resque workers. Once the …
My understanding is that you can use the tokens to log in or to hit arbitrary pages that need authentication, even with cURL. If you look in config/initializers/devise.rb, there should be a line that says something like: config.token_authentication_key = :auth_token Whatever the name of the token_authentication_key is should match what you put as the query …
As an update — GitHub have moved to Resque on Redis instead of Delayed job. However they still recommend delayed_job for smaller setups: https://github.com/resque/resque
you need to create the available.html.erb file within the views/bubble/ directory. When the route takes you to that action, it also navigates you to that view, so if you put: <h2>YEP!!!!</h2> as the only line in that file, it should return that to you on the webpage. In the future, you could use rails g …
You’re probably not going to ruin your dev environment. However, you might end up with newer versions of gems than you had before. It depends on how you have defined them in Gemfile. If you’re using entries like: gem “rails” Then you’ll get the latest rails gem, whatever that might be. If you’re using entries …
You need to update / install a version of the rdoc gem that supports the conversion. Then these errors won’t appear during generation of the documentation when you install rails or when you regenerate the documentation. gem install rdoc Then to regenerate the documentation gem rdoc –all –overwrite
I’m pretty sure you can use the Rack::Request object for passing request-scope variables: # middleware: def call(env) request = Rack::Request.new(env) # no matter how many times you do ‘new’ you always get the same object request[:foo] = ‘bar’ @app.call(env) end # Controller: def index if params[:foo] == ‘bar’ … end end Alternatively, you can get …
You can use and_yield to make rspec call the block passed to the mock: MyClass.stub(:find_each).and_yield(one_mock).and_yield(two_mock)
Close – you most likely want the following: add_index :person_products, [:person_id, :product_id], :unique => true add_index :person_products, :product_id The :unique => true is not strictly required and it depends whether or not it makes sense to have a person associated with a product multiple times. I would say if you’re not sure, you probably do …