Docker wrapper referenced in README is based on a fork

[typpo]

First, thank you all for your work on this excellent project.

The README references a docker wrapper that builds off a forked version of this repository at https://github.com/onesdk/url-to-pdf-api.

This is a bit misleading as it is 52 commits behind master, which means new fixes and features such as image rendering are not available. In the worst case, promoting a Docker image based on a fork could be a security risk.

Are you open to a PR to add a Dockerfile to this repository, or link to another Docker image that is based directly on this repository?

[kimmobrunfeldt]

Good catch. I'd be willing to add a Dockerfile here.

[BobCashStory]

did a pr for this : #142

[AubreyHewes]

@BobCashStory @kimmobrunfeldt

This issue seems to be superseded/resolved by actual changes to the README.md.

The current referenced docker image is not using a fork, the referenced docker image is actually very usable and clones the master of this repo on build. How actual the image is, is up to interpretation.

• https://hub.docker.com/r/restorecommerce/pdf-rendering-srv/tags
• https://docs.restorecommerce.io/pdf-rendering-srv/index.html

I am not saying this project should not have it's own docker image, but that this issue is moot 🐄 .