Will do, thanks Jan.

I was receiving an error earlier on about Lambda not supporting the image - I solved that by doing the following (note the first line).

FROM public.ecr.aws/lambda/nodejs:12
FROM jsreport/jsreport:2.10.0
COPY --chown=jsreport:jsreport jsreports/data /app/data
COPY --chown=jsreport:jsreport jsreports/license-key.txt /app
COPY --chown=jsreport:jsreport jsreports/jsreport.config.json /app
CMD ["sh", "-c", "cp -R /app/data /tmp/data&&node server.js"]

Interestingly, though, I have since removed the first dependency and the function continues to work.

Thanks for your help.

Hi Jan,

The above tutorial was beginning to be complicated, as we have a dependency on phantomJS 1.9.8. We've been trying the image route thanks to the provided image of jsreports-2.10.0-full.

That being said, the lambda function did operate as expected when using the base example provided.

Is it possible to get the image working on AWS lambda, or is it not advisable?

Hi there,

We are doing a POC to host our JSreport instance on AWS Lambda instead of our more traditional VMs.

Following this page here: https://jsreport.net/learn/docker#customize-docker-image

I've got the template working as expected - we have it behind our existing API gateway, it is creating the lambda function, and almost working entirely.

The issue is that when we send a request to the lambda function, the jsreport server appears to immediately fail. The logs indicate that the reporter is initialized, and following, throws this error:

Runtime exited without providing a reason Runtime.ExitError

I believe we're missing a piece, but I don't quite know what.

Below is our dockerfile as well as our jsreport.config.json - please let me know what we're doing wrong!

Dockerfile

FROM jsreport/jsreport:2.10.0
COPY --chown=jsreport:jsreport jsreports/data /app/data
COPY --chown=jsreport:jsreport jsreports/license-key.txt /app
COPY --chown=jsreport:jsreport jsreports/jsreport.config.json /app
CMD ["sh", "-c", "cp -R /app/data /tmp/data&&node server.js"]

Config

{
  "httpsPort": 5488,
  "allowLocalFilesAccess": true,
  "store": {
      "provider": "fs"
  },
  "blobStorage": {
      "provider": "fs",
      "dataDirectory": "/tmp/storage"
  },
  "logger": {
        "file": {
            "silent": true
        },
        "error": {
            "silent": true
        }
  },
  "extensions": {
     "licensing": {
         "useSavedLicenseInfo": false
     },
     "authentication": {
         "enabled": false
     },
     "authorization": {
         "enabled": false
     },
     "cli": {
         "enabled": false
     },
     "express": {
         "enabled": false
     },
     "freeze": {
         "enabled": false
     },
     "fs-store": {
         "dataDirectory": "/tmp/data"
     },
     "import-export": {
         "enabled": false
     },
     "public-templates": {
         "enabled": false
     },
     "sample-template": {
         "enabled": false
     },
     "studio": {
         "enabled": false
     },
     "studio-theme-dark": {
         "enabled": false
     },
     "tags": {
         "enabled": false
     },
     "version-control": {
         "enabled": false
     }
  }
}

Hey Jan,

Strangely, I re-deployed the code via elastic beanstalk and it worked as expected without any errors. I will update this thread if it appears again.

Thanks!
Tyler

Hello,

We are beginning to host an EC2 instance on AWS Elastic Beanstalk / EC2. The JSReport server works as expected while using the developer portal - but, when we attempt to hit the API (api/report/) we get the following error:

ENOENT: no such file or directory, open '/tmp/jsreport/autocleanup/ed1fc487-b093-4ccf-879f-b236e0c4d188html.html'

I have confirmed that the EC2 instance does not have the folder /tmp/jsreport.

Is there a configuration change that must be made?

Thank you!
Tyler

Thank you much, Jan!

Hello!

We use jsreports to generate very large reports (750+ pages), and have found that phantomjs v1.9.8 has been the fastest recipe. Chrome-pdf by default will time out, as many other recipes.

The release notes for the latest version mention that the executable file is much faster than it was previously. It brought conversations for our team recognizing that maintaining node/npm on the server is painful and if the .exe had similar/better performance than node, we would ideally be able to switch.

Unfortunately, while following the instructions to plug in the extension, we are getting a fatal error. Using npm on another folder, we install jsreport-phantom-pdf and place the node modules into a package.

We are unable to get around this error:

Are we incorrectly installing the package as an extension? "discover" is enabled in the configuration, and it is properly attempting to load.

Thank you for your time,
Tyler

Apologies, as I'm pretty inexperienced with Node.

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'.

Got it working locally - the reinstall worked.

When I attempt to install/run the instance on the target machine, though, the terminal responds with "jsreport is not a recognized internal or external command". There is no exe in this file structure.

Is there a file to run hidden somewhere in the node_modules?

The target machine is unable to have node package installed on it. Is it still possible to run a node instance jsreport when the target machine does not have the packages installed via npm?

Also, our ideally the target machine will have the server run as a service. Attempting this locally with the npm installation returns this message: "To install app as windows service you need to have a "start" script or a "main" field in package.json file". Could you share more info about that?

Many thanks as always!