ruby-on-rails-3.1

I'm starting a new project in Rails, and it looks like the application.js manifest file is doing something funny with the javascripts that I reference - does it cache those files as part of the asset pipeline? Here's what happened. I added a javascript file named jquery.autoresize.js to the vendor/assets/javascripts folder, and then referenced the file in the application.js manifest like this: //= require jquery.autoresize.js Then I started up the rails server. But after navigating around in my app, I realized that I had accidentally added the wrong version of the jquery.autoresize.js file. So

I prefer not to concatenate JavaScript files in development mode, but serve them as individual files. So I configured: development.rb: config.assets.compress = false config.assets.debug = true config.assets.compile = true In my /app/assets/javascript directory I have: reviews.js reviews/ foo.js bar.js reviews.js: //= require jquery //= require jquery_ujs //= require_tree ./reviews I include the JavaScript using <%= javascript_include_tag "reviews" %> in my layout. The generated page correctly references the three scripts individually and reviews.js is essentially empty. So far so good. Now

Can someone tell me if I'm just going about the setup the wrong way? I have the following models that have has_many.through associations: class Listing < ActiveRecord::Base attr_accessible ... has_many :listing_features has_many :features, :through => :listing_features validates_presence_of ... ... end class Feature < ActiveRecord::Base attr_accessible ... validates_presence_of ... validates_uniqueness_of ... has_many :listing_features has_many :listings, :through => :listing_features end class ListingFeature < ActiveRecord::Base attr_accessible :feature_id, :listing_id belongs_to :feature

I started making a Rails 3.1 engine, and I'm having a hard time testing it using rspec. First of all, if I run rails g integration_test whatever it creates a regular integration test in tests/integration instead of spec/requests (the rspec-rails gem is installed and required as a development dependency in the gemspec file) Also, when I run a spec test I get an error saying the table corresponding to the model I'm testing has not been created. I tried rake engine_name:install:migrations and running rake db:migrate from inside the dummy app, and I get a "table already exists" error. Everything

Does anyone know how to add another folder to the asset pipeline in Rails 3.1? I'd like to serve app/assets/fonts the same way app/assets/images is served. Update: 5-7-2013 Just to add some clarification for future people who find this question to explicitly add an asset path, in your application.rb file: config.assets.paths << "#{Rails.root}/app/assets/fonts" However, since the above path is under app/assets you don't have to add it explicitly, you just need to restart your rails app so Sprockets can pick it up. You will have to explicitly add paths that are outside of app/assets , lib/assets

I'm getting this error: rake aborted! Could not find a JavaScript runtime. See https://github.com/sstephenson/execjs , I have already spent more hours searching google then I am willing to admit. I believe this is an execJs bug. From all the posts, this is a very common issue with rails 3.1. A js runtime is now needed by what are now standard gems like coffee-script and sass. Most of these cases were resolved by adding the gems 'execjs' and 'therubyracer' to the app Gemfile, and then running 'bundle update' and/or 'bundle install'. But not for me. I guess I got lucky. I am running rails 3.1.3

This is a problem with the cookies collection in a controller spec in the following environment: rails 3.1.0.rc4 rspec 2.6.0 rspec-rails 2.6.1 I have a simple controller spec that creates a Factory user, calls a sign in method which sets a cookie, and then tests to see if the signed in user may access a page. The problem is that all cookies seem to disappear between the authentication cookie being set and the "show" action being called on my controller. My code works fine when run in a browser on the rails dev server. The even stranger behavior while running the spec is that everything set