search

vigetlabs / gulp-rails-pipeline

Ditch the Rails Asset Pipeline and roll your own with Gulp
MIT License
646 stars 64 forks source link

Assets not updating on Heroku #24

Closed danielboggs closed 9 years ago

danielboggs commented 9 years ago

After the initial deployment of this example repo to Heroku, making further edits to the Gulp Sass assets and re-deploying seems to have no impact on the production css. I am able to purge the Heroku repo cache (using: https://github.com/heroku/heroku-repo) and then force another deployment to see the updates but this shouldn't be required. It seems the assets being built to /public/assets are part of the compiled slug and don't get updated unless the slug gets re-compiled.

Navigating directly to my example's assets/stylesheets/global.css file on Heroku, I can see that the styles mirror what was present on the initial deployment and not what the updated Gulp build should reflect.

danielboggs commented 9 years ago

Closing as a duplicate of: https://github.com/vigetlabs/gulp-rails-pipeline/issues/6