nekopanic / buildpack-slug-cleaner

Tidy up your Heroku slugs

Slug cleaner buildpack

This buildpack helps large applications get in under the Heroku size limit. It extends .slugignore to allow the ! prefix and repurposes it to mean "run after the build", preventing files from reaching the final slug. Add it to the end of your buildpacks list so it runs last:

$ heroku buildpacks:add https://github.com/stevo550/buildpack-slug-cleaner.git

Many apps might like to add this to their .slugignore file:

# Rails asset pipeline cache won't be touched in production
!tmp/cache
# App images should have been compiled into public/
!app/assets/images
# Known useless files and directories
!wkhtmltopdf-darwin-x86
!wkhtmltopdf-linux-x86

The easiest way to investigate slug sizes is to do a heroku run bash on the last passing build and du -hs * from there. Slug sizes are usually something that increase over time, so you might find something useful even off a successful build.

If you find any good suggestions for other languages and frameworks send in a pull request or issue and I'll add it to the above.

buildpack-slug-cleaner's Issues

** required?

I wonder what use this thing actually is. It does make things pretty complicated.

sed: couldn't flush stdout: Resource temporarily unavailable

It seems like when the directory it's removing is large (large tmp/cache or /node_modules), I end up with this sed error:

sed: couldn't flush stdout: Resource temporarily unavailable

Also, the verbose flag on rm is causing so much to be logged that when I try to view the deploy log on Heroku, Chrome exhausts my ram and I have to kill the tab.

Perhaps we can turn off the verbose or only pipe to sed on root directories for that slug ignore directory.

Syntax error in Heroku build log

Noticed the following in Heroku build log after adding buildpack-slug-cleaner to buildpacks:

-----> Slug cleaner buildpack app detected
/app/tmp/buildpacks/af2d83ae6592f0b44cba3ea6663183993cd1216fb49e34ffff4ca8928557c92236d4a9a29ca887242d5670e989ac04012ff3396bd26d1ba48eeac512885c01b7/export: line 7: unexpected EOF while looking for matching `"'
/app/tmp/buildpacks/af2d83ae6592f0b44cba3ea6663183993cd1216fb49e34ffff4ca8928557c92236d4a9a29ca887242d5670e989ac04012ff3396bd26d1ba48eeac512885c01b7/export: line 8: syntax error: unexpected end of file

Not sure how this is error is being generated or if it matters (the build succeeds).