Since the upgrade in #128, the gem wkhtmltopdf-binary had an increase in size of about 150Mb. This made impossible to deploy the upgraded app to Heroku since the compressed app would be of over 500Mb.
This problem has also been referenced in their github, as we can see in this issue, and that comes from a prior versions.
The wkhtmltopdf-binary downloads loads of compressed binaries, and the uses the one for the platform it's running in. Another workaround would be to use a buildpack to remove the unnecessary zips before the compressing step in heroku. That way we could get to a smaller footprint, then having an improved deploy of the application.
Since the upgrade in #128, the gem
wkhtmltopdf-binaryhad an increase in size of about 150Mb. This made impossible to deploy the upgraded app to Heroku since the compressed app would be of over 500Mb.Here you can see the size of the different versions, and the huge increase between v0.12.6.6 and v0.12.6.7 https://rubygems.org/gems/wkhtmltopdf-binary/versions/0.12.6.6
This problem has also been referenced in their github, as we can see in this issue, and that comes from a prior versions.
The
wkhtmltopdf-binarydownloads loads of compressed binaries, and the uses the one for the platform it's running in. Another workaround would be to use a buildpack to remove the unnecessary zips before the compressing step in heroku. That way we could get to a smaller footprint, then having an improved deploy of the application.