Rake::Sprockets
Very easy defaults for using sprockets through rake.
Installation
Add this line to your application's Gemfile:
gem 'rake-asset-pipeline'
And then execute:
$ bundle
Or install it yourself as:
$ gem install rake-asset-pipeline
Usage
The default expected folder structure is:
assets/
js/app.js
css/app.css
public/
Build the assets with:
$ rake build
This will produce the following new files:
public/assets/js/app.js
public/assets/css/app.css
Override defaults
These are the settings that can be overriden in your Rakefile
:
Project root
The default is Dir.pwd
.
Rake::Sprockets.root = Pathname.new __dir__
logger
The default is $stdout
.
Rake::Sprockets.logger = Logger.new("log/output.log")
env
#env
is set to RAKE_ENV
or defaults to development.
#env
is fancy and can answer queries:
Rake::Sprockets.env.production?
Override from the shell:
$ RAKE_ENV=production rake build
precompile list
The default is to only compile app.js
and app.css
. You can add more
files:
Rake::Sprockets.precompile += ["other.css", "cray.js"]
asset directories
The default asset directories are assets/js
and assets/css
. You can
change or add more:
Rake::Sprockets.asset_paths = ["stylesheets", "javascripts"] # "assets/" is prepended
compression
In production compression is used if it's setup. You need to supply the js and css compressors (there are no defaults):
Rake::Sprockets.css_compressor = :sass
Rake::Sprockets.js_compressor = :uglify
Contributing
- Fork it ( https://github.com/myobie/rake-sprockets/fork )
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Add some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create a new Pull Request