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.
Sorry for the late response here but my days have been very busy. I think you are 100% correct that the binaries got corrupted. After deleting the folder and re-running the report, everything worked fine and I had zero issues deploying to another server. Not sure entirely what all is happening but deleting the folder and re-trying seemed to solve the issue.
Again, apologies for the delayed response - but I did want to follow back up on this to ensure other people might come across the (hopefully temporary) solution.
Thanks for your prompt response!
Disabled Categories are greyed out
This topic will be moved to the category
Looks like your connection to jsreport forum was lost, please wait while we try to reconnect.