You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying to Heroku, Bootstrap's Glyphicons cannot be found by the browser. As a consequence, all Glyphicons will be replaced with an empty box.
It looks like this is a frequent problem with ruby builds on Heroku, but I couldn't find any mention of the issue for Javascript. I believe it is caused by the minify step.
Edit:
It looks like one of two things will have to be done. Either move the fonts file into the public/build/ directory after running bower install, or after bower has run, modify the minified CSS file to point to the original fonts location. The second way seems extraordinarily hacky/error prone.
As for moving the fonts file; it should be possible with a simple fs.rename(...). Anyone know where in the build process would be the most appropriate place to do this? It will need to be done after bower has loaded bootstrap, but before slug compilation has completed.
The text was updated successfully, but these errors were encountered:
When deploying to Heroku, Bootstrap's Glyphicons cannot be found by the browser. As a consequence, all Glyphicons will be replaced with an empty box.
It looks like this is a frequent problem with ruby builds on Heroku, but I couldn't find any mention of the issue for Javascript. I believe it is caused by the minify step.
Edit:
It looks like one of two things will have to be done. Either move the fonts file into the public/build/ directory after running bower install, or after bower has run, modify the minified CSS file to point to the original fonts location. The second way seems extraordinarily hacky/error prone.
As for moving the fonts file; it should be possible with a simple fs.rename(...). Anyone know where in the build process would be the most appropriate place to do this? It will need to be done after bower has loaded bootstrap, but before slug compilation has completed.
The text was updated successfully, but these errors were encountered: