By default Rails assumes that you have your files precompiled in the production environment, if you want use live compiling (compile your assets during runtime) in production you must set the config.assets.compile to true. # config/environments/production.rb … config.assets.compile = true … You can use this option to fallback to Sprockets when you are using precompiled … Read more
For turbolinks 5.0 you must use the turbolinks:load event, which is called the first time on page load and every time on a turbolink visit. More info: https://github.com/turbolinks/turbolinks#running-javascript-when-a-page-loads CoffeeScript code: $(document).on ‘turbolinks:load’, -> my_func() JavaScript code: document.addEventListener(“turbolinks:load”, function() { my_func(); })
Heroku’s asset plugins no longer work since Rails 4 does not support plugins. You need to use Heroku’s asset gems instead. Place this in your Gemfile: group :production do gem ‘rails_log_stdout’, github: ‘heroku/rails_log_stdout’ gem ‘rails3_serve_static_assets’, github: ‘heroku/rails3_serve_static_assets’ end Follow Heroku’s guide on getting started with Rails 4. Update (07/22/2013): Heroku now supplies a different gem … Read more
In production mode, Rails will not be responsible for serving static assets. Therefore, you are getting this error. Thin won’t do it either, since it’s just a wrapper around Rails. This is controlled by this setting in config/environments/production.rb in your application: config.serve_static_files = false Or in Rails 5: # config/environments/production.rb config.public_file_server.enabled = true Or set … Read more
Previously the assets group existed to avoid unintended compilation-on-demand in production. As Rails 4 doesn’t behave like that anymore, it made sense to remove the asset group. This is explained in more detail in the commit that changed that. I extracted some quotes with the actual answer. Some gems can be needed (in production) like … Read more
I’ve discovered a way to make it less rigid and future proof by still using the asset pipeline but having the stylesheets grouped. It’s not much simpler than your solution, but this solution allows you to automatically add new stylesheets without having to re-edit the whole structure again. What you want to do is use … Read more
To load only the necessary name_of_the_js_file.js file: remove the //=require_tree from application.js keep your js file (that you want to load when a specific page is loaded) in the asset pipeline add a helper in application_helper.rb def javascript(*files) content_for(:head) { javascript_include_tag(*files) } end yield into your layout: <%= yield(:head) %> add this in your view … Read more
Place the following code in config/initializers/quiet_assets.rb if Rails.env.development? Rails.application.assets.try(:logger=, Logger.new(‘/dev/null’)) Rails::Rack::Logger.class_eval do def call_with_quiet_assets(env) previous_level = Rails.logger.level Rails.logger.level = Logger::ERROR if env[‘PATH_INFO’] =~ %r{^/assets/} call_without_quiet_assets(env) ensure Rails.logger.level = previous_level end alias_method_chain :call, :quiet_assets end end Updated: It now works for Ruby on Rails 3.2 too (previous attempt fixes before_dispatch, and now we’re going for the … Read more
My friend was attempting a Rails tutorial on Win 8 RTM a few months ago and ran into this error. Not sure if this issue exists in Windows 7 as well, but this may help. Options: 1) Removing //= require_tree . / Ignoring the issue – As ColinR stated above, this line should not be … Read more
If your Rails version is between > 3.1.0 and < 4, place your fonts in any of the these folders: app/assets/fonts lib/assets/fonts vendor/assets/fonts For Rails versions > 4, you must place your fonts in the app/assets/fonts folder. Note: To place fonts outside of these designated folders, use the following configuration: config.assets.precompile << /\.(?:svg|eot|woff|ttf)\z/ For Rails … Read more