3 ms·
No problem! FYI there may be something else bloating your slug. With the ruby buildpack, heroku by default will install node_modules to a shared cache directory
by schneidmaster 6y ago
No problem! FYI there may be something else bloating your slug. With the ruby buildpack, heroku by default will install node_modules to a shared cache directory and not include them in the slug artifact. For example I have a Rails app that has 250MB of node_modules locally but my slug on Heroku is only 93.4MB.
- rileytg 6y agoGood to know, Ill keep digging on the heroku side.
- schneidmaster 6y agoActually, I guess I was wrong about node_modules not being included in the slug -- it's just that the slug is compressed so node_modules don't take up anything close to their stat size. One common gotcha is that if you have large non-code files in your git repo (binaries/images/gzips/etc), those will end up in your slug and they don't compress well so they'll add a lot of bloat. If that's the case you can use a .slugignore file[0] to tell Heroku to exclude them. Good luck! [0]: https://devcenter.heroku.com/articles/slug-compiler#ignoring-files-with-slugignore https://devcenter.heroku.com/articles/slug-compiler#ignoring...