So you now use your local jsreport instance started using node.js and it is now running as a web server?
In this case, it is better to use jsreport.Client and connect to it.
Oh, and if I follow the link you linked to it, I will be able to set it up? Because for some reason this js report node is just timing out every html request I send to it.
Binaries are typically not faster than full jsreport running through node.js as web server.
Oh, it does make sense that they are faster though, since machine code works fast
What kind of arguments do you mean?
this one: chrome_launchOptions_args=--no-sandbox and if I should set it up for using non root/sudo then I don't know how to do that either.
Not an expert on this topic. However, maybe you should let the reverse proxy deal with https and abstract it out from your application.
Your application would be then running just http and you don't need sudo for it.
My reverse proxy autoswitches http to https, and I think it should do that by default as well, so no biggie there. It's a long time since I visited this though. So can't quite remember everything.