31–40 of 58 posts
Earlier quoted context omitted.
Just a digital ocean droplet running FreeBSD, then PM2 running Node.JS and ImageMagick built with multicore support.
ImageMagick with "multicore" support won't speed things up the moment number of concurrent requests touches the number of cores you have. And in digital ocean's case you have only one core.
Actually it just uses ImageMagick and soffice under the hood, so it can do way more than PDF. I've tested it with DOC, DOCX, XLS, and they all seem to work. Edit: in case anyone wants an example, here's the conversion of tesla-model-s.pdf[0]: https://secureview.cloudbrowser.xyz/uploads/filekat9.v05lnle... [0]: https://www.tesla.com/sites/default/files/tesla-model-s.pdf
Does it support SVG?
Earlier quoted context omitted.
My experience is relatively small. The `convert` script of ImageMagick calls soffice by default if the input file is a LibreOffice type. I actually started writing a shell script to detect if it was DOCX etc, and run soffice first, but then I found out that ImageMagick does that automatically, if libreoffice is installed.
hmm, OK, I didn't know that. Thanks that's useful :) Be interesting to see how your demo site holds up under HN front page traffic - I know Imagemagic is used a lot for random web sites, but I worry about scale a lot. Any info would be useful!
Earlier quoted context omitted.
hmm, OK, I didn't know that. Thanks that's useful :) Be interesting to see how your demo site holds up under HN front page traffic - I know Imagemagic is used a lot for random web sites, but I worry about scale a lot. Any info would be useful!
no probs. if you want to email me I can let you know once it all quiets down.
Earlier quoted context omitted.
OK, that's a good point. I think the only reason was I looked at PDF.js and felt the quality was not so good, and then I tried ImageMagick and found it gave good quality, so I just went with that. Another reason is I made this to convert the PDF (or Word doc, XLS, etc) remotely without the file ever touching the user's device. So they couldn't be exposed to any exploits contained in the file or of the PDF engine (PDF…
"to convert the PDF (or Word doc, XLS, etc) remotely without the file ever touching the user's device" This made me think that the site accepts a URL to a PDF/XLS/DOC file and returns PNG.
Actually, that is basically what happens in the original context for this service.
If you take a look at
open a remote browser, then search for a PDF/XLS/DOC etc and then click on it, you'll see a dialog which says the file is transferred.
What's happening is the remote browser downloads the file to a temp directory in the cloud, then some software does a POST request with that file to the service (Simple PDF to PNG Server) and gets the viewing link back immediately, before the conversion has completed.
It then sends the viewing link back to the remote browser which opens a tab. The client can then view the document as images securely without the file ever touching their device.
Originally, I didn't intend to release this viewer as a separate thing/product/service.
If you use the viewer (without the remote browser) you do have to submit the file. I didn't make it to fetch them. I made it as a "secure document viewer" for the remote browser product.
With superb open source, cross platform libraries like pdfium available to the public, why won't I just do this on the client?
It can start to bog down with large image heavy pdfs. But overall it runs performantly.
Do this with plot files and dxf's and you can sell it
Actually it just uses ImageMagick and soffice under the hood, so it can do way more than PDF. I've tested it with DOC, DOCX, XLS, and they all seem to work. Edit: in case anyone wants an example, here's the conversion of tesla-model-s.pdf[0]: https://secureview.cloudbrowser.xyz/uploads/filekat9.v05lnle... [0]: https://www.tesla.com/sites/default/files/tesla-model-s.pdf
what's your experience running soffice server-side? I might have to do this soon, and I'm dreading it.
Earlier quoted context omitted.
Just a digital ocean droplet running FreeBSD, then PM2 running Node.JS and ImageMagick built with multicore support.
ImageMagick with "multicore" support won't speed things up the moment number of concurrent requests touches the number of cores you have. And in digital ocean's case you have only one core.
(At the possible cost of top-end scale; improving response to normal workload significantly and hurting the top workload reachable somewhat).