# webpack-rails-buildpack

A buildpack to support Heroku deployments with [webpack-rails](https://github.com/mipearson/webpack-rails).

## Installation

Add a custom buildpack to your to your applications Settings tab under
Section Buildpacks, using the URL of this repository, instead of the
short name of Heroku's own buildpacks. Put:

    https://github.com/febeling/webpack-rails-buildpack.git

It can in last position.

## Usage

On deployment, the buildpack runs the build command `bundle exec rake
webpack:compile`. Under default configuration that will output the
compiled assets under `public/webpack`.

## Contributing

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. Submit a pull request :D

## History

Started on 5 June 2016.

## Credits

Created by Florian Ebeling.

## License

See LICENSE.md file.

# webpack-rails-buildpack

A buildpack to support Heroku deployments with [webpack-rails](https://github.com/mipearson/webpack-rails).

## Installation

Add a custom buildpack to your to your applications Settings tab under
Section Buildpacks by using the URL of this repository, instead of the
short name of Heroku's own buildpacks. From the command line run:

    heroku buildpacks:add https://github.com/febeling/webpack-rails-buildpack.git

It can be in last position.

## Usage

On deployment, the buildpack runs the build command `bundle exec rake
webpack:compile`. Under default configuration that will output the
compiled assets under `public/webpack`.

## Contributing

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. Submit a pull request :D

## History

Started on 5 June 2016.

## Credits

Created by Florian Ebeling.

## License

See LICENSE.md file.

Edit and add command line usage
Edit and add command line usage