Adding bowerify gem to fix the issue with relative assets paths in bower components

README.md

@@ -84,7 +84,7 @@ asset "secret_logic", "1.0.0", git: "[email protected]:initech/secret_logic"
 # get from a github repo
 asset "secret_logic", "1.0.0", github: "initech/secret_logic"
 
-# get a specific revision from a git endpoint 
+# get a specific revision from a git endpoint
 asset "secret_logic", github: "initech/secret_logic", ref: '0adff'
 ```
 
@@ -171,10 +171,6 @@ will ignore the `directory` property and instead will use the automatically gene
 
 [Bower](https://github.com/bower/bower) should be installed using npm. Bower can be installed globally (with `$ npm install -g bower`) or in `node_modules` in the root directory of your project.
 
-##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.
-
 Remember that you should have [bower installed](#bower-installation) either locally in your project or on a remote server.
 
 ##Bower Main Files

bower-rails.gemspec

@@ -17,7 +17,9 @@ Gem::Specification.new do |s|
   s.require_paths = ["lib"]
   s.license    = 'MIT'
 
+  s.add_dependency "bowerify"
+
   s.add_development_dependency "rspec"
   s.add_development_dependency "rake"
   s.add_development_dependency "coveralls"
-end
+end

lib/bower-rails/railtie.rb

@@ -20,6 +20,8 @@ class Railtie < Rails::Railtie
         ["lib", "vendor"].each do |dir|
           app.config.assets.paths << Rails.root.join(dir, 'assets', 'bower_components')
         end
+
+        app.config.bower_components_path = Rails.root.join('lib', 'assets', 'bower_components')
       end
     end