Hacker News new | ask | show | jobs
Show HN: Automatically fill PDF templates per API (doqs.dev)
22 points by dnnsthnnr 1407 days ago
3 comments

I've been looking for a library similar to this. Love the idea, but cannot post to SaaS. Too bad it's subscription only
Then you might be interested in my application that I posted here the other day. It's mainly a GUI application for power users, but it also has a console application so you can integrate it into your workflow. The JSON support I had added as an additional feature, but to my knowledge it is not used by anyone yet (at least I had no support mails about it). Oh, and it works without cloud and can be used completely offline (after one-time online activation, if you want to remove the demo watermark).

https://news.ycombinator.com/item?id=31999358

Why can't you post to a SaaS? Would love to know more.
Guessing data security constraints -- I'm likely in a similar boat.
I am curious what is your tech setup? Running on the dedicated server or cloud, which programming languages and libraries are you using?
I am running on python and AWS Lambda. Works really smooth battle tested it with 100 pdf pages and 400 fields to be merged and the Pdf is generated within 2 seconds. And I am currently using one of the lowest resource settings on AWS Lambda.

I am mostly using pikepdf and the a lot of secret sauce added ;)

I am not OP but pdftk is one of the best libraries I found for this. You can package the binary and run it on a server somewhere.
Awesome idea, but website seems unstable. Wasn't able to login after sign-up :/
Yes I still have problems with the activation mail. Need to fix this, currently rely on my own SMTP which is not a good idea. Should move to a service.

Is it working for you now?

I'm getting a variety of CORS errors in console. Maybe this helps:

``` Access to XMLHttpRequest at 'https://api.doqs.dev/v1/organization' from origin 'https://app.doqs.dev' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. ```

Omg, thats awkward. Should not have happened. Its working now :)