README.md in bower-rails-0.6.1 vs README.md in bower-rails-0.7.0

- old
+ new

@@ -6,23 +6,25 @@ [![Dependency Status](https://gemnasium.com/SergeyKishenin/bower-rails.png)](https://gemnasium.com/SergeyKishenin/bower-rails) [![Build Status](https://travis-ci.org/42dev/bower-rails.png?branch=master)](https://travis-ci.org/42dev/bower-rails) [![Coverage Status](https://coveralls.io/repos/42dev/bower-rails/badge.png)](https://coveralls.io/r/42dev/bower-rails) Bower support for Rails projects. Dependency file is bower.json in Rails root dir or Bowerfile if you use DSL. -Check out Changelog.md for the latest changes and releases. +Check out [changelog][] for the latest changes and releases. +[changelog]: https://github.com/42dev/bower-rails/blob/master/CHANGELOG.md + **Requirements** * [node](http://nodejs.org) ([on github](https://github.com/joyent/node)) * [bower](https://github.com/bower/bower) (>= 0.10.0) installed with npm **Install** in Gemfile ``` Ruby - gem "bower-rails", "~> 0.6.1" + gem "bower-rails", "~> 0.7.0" ``` ##JSON configuration Bower-rails now supports the standard [bower package](https://github.com/bower/bower#defining-a-package) format out-of-the-box. Simply place your bower.json file the Rails root directory to start. Using the standard format will default all bower components to be installed under the `vendor` directory. @@ -123,6 +125,14 @@ ##Relative asset paths Some bower components (eg. [Bootstrap](https://github.com/twbs/bootstrap/blob/0016c17f9307bc71fc96d8d4680a9c861f137cae/dist/css/bootstrap.css#L2263)) have relative urls in the CSS files for imports, images, etc. Rails prefers using [helper methods](http://guides.rubyonrails.org/asset_pipeline.html#coding-links-to-assets) for linking to assets within CSS. Relative paths can cause issues when assets are precompiled for production. -Before the `rake assets:precompile` task is run, the bower assets will be reinstalled with the relative paths replaced with calls to `asset_path` so that all asset links work in production. +If you would like the bower assets to be reinstalled with the relative paths on every deploy, provide an option for `bower-rails` so it do it automatically before the `rake assets:precompile` task is run: + +``` ruby +BowerRails.configure do |bower_rails| + # By default this option is false + bower_rails.resolve_before_precompile = true +end +``` +Remember that you should have [bower installed](#bower-installation) either locally in your project or on a remote server.