# Asset Pipeline
# Manifest Files and Directives
assets initalizer (
config/initializers/assets.rb) are a few files explicitly defined to be precompiled.
# Precompile additional assets. # application.coffee, application.scss, and all non-JS/CSS in app/assets folder are already added. # Rails.application.config.assets.precompile += %w( search.js )
In this example the
require <path>: The
requiredirective functions similar to Ruby's own
require. It provides a way to declare a dependency on a file in your path and ensures it's only loaded once before the source file.
require_directory <path>: requires all the files inside a single directory. It's similar to
path/*since it does not follow nested directories.
require_tree <path>: requires all the nested files in a directory. Its glob equivalent is
require_self: causes the body of the current file to be inserted before any subsequent
requiredirectives. Useful in CSS files, where it's common for the index file to contain global styles that need to be defined before other dependencies are loaded.
stub <path>: remove a file from being included
depend_on <path>: Allows you to state a dependency on a file without including it. This is used for caching purposes. Any changes made to the dependency file will invalidate the cache of the source file.
application.scss file could look like:
/* *= require bootstrap *= require_directory . *= require_self */
Another example is the
application.coffee file. Here with including
#= require jquery2 #= require jquery_ujs #= require turbolinks #= require_tree .
//= require jquery2 //= require jquery_ujs //= require turbolinks //= require_tree .
# Rake tasks
sprockets-rails is shipped with the following rake tasks:
assets:clean[keep]: Remove old compiled assets
assets:clobber: Remove compiled assets
assets:environment: Load asset compile environment
assets:precompile: Compile all the assets named in
# Basic Usage
There are two basic ways that the asset pipeline is used: