-
Notifications
You must be signed in to change notification settings - Fork 169
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
Comments
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. 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! |
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. |
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. |
if you are using barryvdh/laravel-snappy and h4cc/wkhtmltopdf-amd64, strugling for Image not printing in pdf. https://github.com/wkhtmltopdf/packaging/releases from Offical Website Download page How to Install wkhtmltopdf from Offical Binray? |
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.
The text was updated successfully, but these errors were encountered: