Bowndler

Integrate bower and bundler, by making bower aware of gem bundles.

NOTE:

• this is experimental, your results may vary
• this readme needs to be updated, we know its light on detail. It is highly recommended that you read the source before using bowndler.

Add this line to your application's Gemfile:

gem 'bowndler'

And then execute:

$ bundle

Or install it yourself as:

$ gem install bowndler

1. rename bower.json to bower.json.erb
2. add "my_gem": "<%= gem_path('my_gem') %>" to "paths" in the bower.json.erb, for any gem that has its own bower.json
3. instead of running bower <command>, run bowndler <command> and bowndler will make sure the bower.json is up to date. e.g. bowndler install

1. In the root of your project run bowndler update
2. If your packages are not being updated as expected run bower cache clean first
3. If your packages are still not being updated. Delete the bower_components directory and try again

Bowndler has a somewhat magical "autohook" feature - where bowndler update will run automatically whenever you run a bundle command that could potentially change your Gemfile.lock. This is VERY experimental, and should be used with caution.

To enable it:

1. Run bowndler autohook in the root of your repo. This will modiy your Gemfile, those changes should be committed to source control.
2. Set ENABLE_BOWNDLER_HOOK=1 in your environment (by adding export ENABLE_BOWNDLER_HOOK=1 to your .bashrc or .bash_profile)

NOTE: Autohook only works reliably on Mac OS X. It currently causes a segfault on both Ruby 1.9.* and 2.* on CentOS (and potentially other Linux distributions as well)

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request