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

[kaievns]

hey guys, there is a little gem called bowerify that fixes the relative assets path when you use bower components in rails assets pipeline.

[SergeyKishenin]

Have you tested it with bower-rails? Does it work correctly out of the box?

If yes, do we need resolving stuff anymore, like rake tasks, resolving before precompilation and so on?

[kaievns]

Hey Sergey,

I didn't test it much with bower-rails, but I did tested the bowerify code quite extensively everything seems working just fine. As there is not much of overlap between the two, i figured it should be alright.

as for your resolving tasks, i believe you won't need them anymore, assets precompilation works perfectly with bowerify in my project (i have bootstrap3 and font-awesome) assets get copied and hashed correctly. But again, i didn't test it with bower-rails as i'm not really a user (i'm on vanilla bower)

[SergeyKishenin]

Okay, thanks! So we have to test it first before merge. I'll try to do it asap

[kaievns]

no worries, let me know how did it go. btw, you might wanna create a simple demo project for the gem, so people could test their changes over it properly.

[eddietejeda]

What's the status of this pull request?

[SergeyKishenin]

I've tried to go on working on it but met an issue ninefold/bowerify#2.

Actually, I prefer to implement our own (or extract some logic out of bowerify if it is possible) to close this issue. But now I have lack of time to achieve it.

So, if anyone can help with that — welcome!