But I'm not the biggest fan of the approaches taken by either of those libraries. I would much prefer to function just like sprockets - where it all works without the end user having to modify their code.
To get this to work Breakfast is going to have to generate an asset manifest on deploy. Then the Rails asset tags will probably need to be modified to take the manifest into account.
At the moment there are at least two brunch libraries for adding digests to your assets:
https://github.com/meleyal/git-digest-brunch https://github.com/mutewinter/digest-brunch
But I'm not the biggest fan of the approaches taken by either of those libraries. I would much prefer to function just like sprockets - where it all works without the end user having to modify their code.
To get this to work Breakfast is going to have to generate an asset manifest on deploy. Then the Rails asset tags will probably need to be modified to take the manifest into account.