Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Also provide the CentOS7 binary? #19

Open
rvanlaak opened this issue Apr 19, 2016 · 4 comments
Open

Also provide the CentOS7 binary? #19

rvanlaak opened this issue Apr 19, 2016 · 4 comments

Comments

@rvanlaak
Copy link

We have a problem with deploying our application to Platform.sh, which uses a different OS (debian) as our current production environment does (centos7).

Basically, your repo supports the debian os perfectly but we can not use it for our production environment because that relies on the centos7 package. That's why I've published the centos7 version to Packagist, see https://github.com/rvanlaak/wkhtmltopdf-amd64-centos7

The problem we face is explained at this StackOverflow question, basically we can not install the proper package while publishing the new build.

This would work if your repository would support all binaries, and the correct binary would be symlinked based on an OS check. This would mean adding extra files to your repository, and adding a script that checks the OS before symlinking it. What do you think about this? That would allow me to deprecate my own repository because people can always make use of your repo.

@h4cc
Copy link
Owner

h4cc commented Apr 23, 2016

Hi @rvanlaak, thanks for that info.

I already thought about using a installer script, but in the end this is a problem solved by system package managers like apt or yum already.
In the end this repo is just a "shortcut" for debian/ubuntu based developers to start quickly and it should/can not be more because the effort would be wasted.

What you did seems to do the trick for your problem already and can also help others. And to be honest, instead of using this repo you could commit the wkhtmltopdf binaries (debian/ubuntu/centos/redhat) directly with the source of your project - it would not make much difference. Using a package manager does not have a much different effect in the end.

I am going to add a link to your repo. Thanks!

@rvanlaak
Copy link
Author

I don't like committing external libraries with my own code if Composer is really good at managing it ;-) Basically the big advantage of this repo is that we do not need any package manager anymore and the installed version is isolated for each project.

@softius
Copy link

softius commented Sep 28, 2018

I believe that another option is to use both libraries and create on the fly your own symbolic link without removing composer dependencies. This could be done as a composer post install / update script.

@zgetro
Copy link

zgetro commented May 25, 2022

if you are using barryvdh/laravel-snappy and h4cc/wkhtmltopdf-amd64, strugling for Image not printing in pdf.
or pain to get latest binary then just use latestet binary from Offical gitub release

https://github.com/wkhtmltopdf/packaging/releases

from Offical Website Download page

How to Install wkhtmltopdf from Offical Binray?

Here is reference blog for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants