I've taken the node.exe file from C:\Program Files\nodejs and placed it in the jsreport folder. It is in the same directory as server.js, data, node_modules, etc.
Running the command "node server.js" from the cmd prompt yields the response "cannot find module 'semver'.
The enterprise plan is per jsreport instance. If you have jsreport in 3 containers in 3 zones and it boots up in all of them, you need 3 licenses.
The scale license is here to simplify such scenarios. You get one license key and you don't have to worry how many instances you run.
We may consider in the future an extra license plan for the (hot) servers that aren't actually used and just ready to jump in.
However, for now, we have it in the simple two options form
enterprise license - per instance
enterprise scale license - infinite
I made a clean jsreport on my local and do it again.
Everything works as expected...
So I tried to delete all my node_modules(Including the jsreportapp folder), and run the npm install again, everything is fine now.
I don't know what's the magic, but it is now OK.
yes, although it is very unlikely that we will change the initialization code, i get your point.
let's see if we can add a simple way to run code at the startup, at least it will be good for simple cases, for more complex cases which requires more grained control the best is to do it yourself in your own server.
hi! if your remote server is node.js based and you have already installed jsreport-pdf-sign and jsreport-assets in version 1.1.4 then you can just open the jsreport studio and follow the instructions in the docs https://jsreport.net/learn/pdf-sign. if your remote server is .net based then you can install the new pdf-sign using the instructions here.
After this i think you won't need to modify anything in your jsreport remote client call code, if you configure the pdf-sign options using the studio then you should be able to render the report using the same code that you have already for the jsreport remote client
so your solution is a good one.. I will move to use this package and change my fs.writeFileSync to use this package (which seems to do your solution under the covers) and will handle this .. good call.
The templates are by default stored inside the docker container.
When you recreate the container, templates are lost.
You can mount your external directory to the container to let it persist templates there.
See the docker readme "Persist templates" https://hub.docker.com/r/jsreport/jsreport/