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

Release to Rubygems #17

Closed
butzopower opened this issue Sep 11, 2014 · 22 comments
Closed

Release to Rubygems #17

butzopower opened this issue Sep 11, 2014 · 22 comments
Milestone

Comments

@butzopower
Copy link
Collaborator

No description provided.

@butzopower butzopower added this to the 0.12 Release milestone Sep 11, 2014
@dalibor
Copy link

dalibor commented Oct 20, 2014

Would be nice to have 0.12 released on rubygems.

@JacobEvelyn
Copy link

Seconded! We're using our own cloned version of this repo with git history erased to get around this in the meantime (using this repo directly in our Gemfile pushes us over Heroku's compiled slug size limit, because of all of the binaries in this repo's git history).

@richardwan
Copy link

release to ruby gems would be great. the current version on ruby gems has which binaries fails to detect stylesheets and images on any pages on an https site which no longer supports the broken ssl 3.0 protocol. wkhtmltopdf/wkhtmltopdf#1999

what this means is that when servers get patched (to protect themselves against the poodle attack) pdfs will lose all their stylesheets and images and devs will be wondering why the pdfs which worked fine one day just stopped working perhaps with no changes committed to the code base.

@diresquirrel
Copy link

Would be amazing to get this released via Rubygems. Had to write a bunch of code to tackle http vs https for pdf generation in response to updating our servers for the poodle vulnerability. Is there an ETA?

@zakird
Copy link
Owner

zakird commented Oct 31, 2014

Hi All. Sorry we've been MIA. I haven't had a chance to look at what's going on. Is this just a matter of deploying new binaries? My last understanding was that some of the binaries weren't working on all OS'es? Has this been fixed, or are we moving on?

In full disclosure, I am not in a fantastic spot to be maintaining this gem (I haven't used it in ~5 years and am not up-to-date with what's going on in this space). If someone is willing and able to take over and carry on the project, it would make sense to transfer ownership of this project to someone more appropriate.

@unixmonkey
Copy link
Collaborator

@zakird I'd be glad to help out. I'm already doing primary maintenance and support for https://github.com/mileszs/wicked_pdf

@zakird
Copy link
Owner

zakird commented Nov 4, 2014

@unixmonkey that sounds great. can you shoot me an email zakir@umich.edu?

@toncid
Copy link

toncid commented Nov 21, 2014

+1

1 similar comment
@rposborne
Copy link

+1

@marnen
Copy link

marnen commented Feb 6, 2015

+1. Can I help?

@bigtunacan
Copy link

It's been almost a year since this was opened; is anyone looking into this?

@toncid
Copy link

toncid commented Jun 10, 2015

If you are using Heroku, I'd suggest switching to this: https://github.com/rafaelp/heroku-buildpack-wkhtmltopdf

@rposborne
Copy link

Or https://github.com/rposborne/wkhtmltopdf-heroku, which really is just, wkhtmltopdf built for LTS ubuntu.

@bigtunacan
Copy link

@toncid @rposborne I'm on company VMs.

@rietta
Copy link

rietta commented Jun 18, 2015

Just ran into this with an older project today. It was a real head scratcher, digging down to running wkhtmltopdf at the command line to disable the quiet flag and testing many images from HTTP and HTTPS sites to narrow down what was happening to cause it to fail silently.

Deploying from the master branch works; but it would be nice to see the updated build pushed to Rubygems.

@andyh
Copy link

andyh commented Jun 25, 2015

I too have run into this same problem today with an older project. Can we get this pushed to rubygems?

@MichaelSp
Copy link

I'm just here to give my +1
Please, release asap.

@rposborne
Copy link

@bigtunacan no worries the heroku gem, is actually poorly named. It can run on any 14.04 ubuntu server. (we currently run it on our own bare metal)

@marnen
Copy link

marnen commented Oct 15, 2015

This issue has been open for over a year. What is the holdup?

@DannyBen
Copy link

Why isn't this happening?
Both the repository and the owner seem to be active, but the gem is not released with the newer binaries.

I am using the alternative edge fork for now, but I am curious about the state of this gem and would prefer to use the canonical.

@unixmonkey
Copy link
Collaborator

0.12.3 has been released to rubygems.org! Please open another issue if you have any problems.

@roolo
Copy link

roolo commented Jul 14, 2016

@unixmonkey Ty a lot

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