Hi

I am trying to deploy Koolreport to Laravel Vapor. This is an implementation of Laravel hosted in a serverless environment using AWS Lambda.

At first, when I tried running a report I got ErrorException: Undefined index: SCRIPT_NAME at /vendor/koolreport/core/src/core/Utility.php line 491. The reason was that there was no $_SERVER['SCRIPT_NAME'] variable defined in the environment. As a workaraound, I am running the following code prior to running the report (I might consider raising a PR for this):

    if (!array_key_exists("SCRIPT_NAME", $_SERVER)) {
      $scriptFilename = str_replace("\\","/",$_SERVER["SCRIPT_FILENAME"]);
      
      // Read script_filename backwards until we reach /
      for ($i=strlen($scriptFilename)-1; $scriptFilename[$i]!="/" && $i>0 ; $i--) {
      }

      $_SERVER["SCRIPT_NAME"] = substr($scriptFilename, $i);
    }

Having resolved that issue, I am now getting copy(/var/task/public/koolreport_assets/3157288213/KoolReport.js): failed to open stream: No such file or directory (View: /var/task/resources/views/reports/report.blade.php) at /vendor/koolreport/core/src/core/Utility.php line 92. This line is part of the Utility::recurseCopy() method and reads:

Utility::recurseCopy($src . '/' . $file, $dst . '/' . $file);

The context is

{
  dir: Resource stream, 
  dst: /var/task/public/koolreport_assets/3157288213, 
  file: KoolReport.js, 
  src: /var/task/vendor/koolreport/core/src/clients/core
}

Further investigation reveals that the folder /var/task/public/koolreport_assets/3157288213 doesn't exist, though it's parent (koolreport_assets) does (at, at the time of debugging, so was koolreport_assets/3460555030.

Is there anything that I can do prior to running the report (or ideally at deployment time) to prevent this copy from occurring? And where does the folder name 3157288213 come from?

Finally, are there any other known issues deploying to Laravel Vapor that I would need to be aware of?

Many thanks Nick

Hi David

Thank you for your kind reply.

My gut feel tells me that the issue is connected with Laravel Vapor's implementation rather than with Lambda per se. Though I may be wrong...

Best wishes Nick

Hi David

The error message from mkdir was mkdir(): Read-only file system, which is not 100% surprising.

One thing I noticed during the deployment to Vapor was that it takes a copy of /public from the local hard drive of my machine. This time, during deployment, I had 3 subfolders under koolreport_assets, namely:

$ ls -lR koolreport_assets
koolreport_assets:
total 0
drwxr-xr-x 1 nresa 197609 0 Dec  1 14:31 162342713/
drwxr-xr-x 1 nresa 197609 0 Dec  1 14:31 3157288213/
drwxr-xr-x 1 nresa 197609 0 Dec  1 14:31 417790547/

koolreport_assets/162342713:
total 13
-rw-r--r-- 1 nresa 197609  156 Dec  1 14:31 table.css
-rw-r--r-- 1 nresa 197609 8512 Dec  1 14:31 table.js

koolreport_assets/3157288213:
total 12
-rw-r--r-- 1 nresa 197609 6211 Dec  1 14:31 KoolReport.js
-rw-r--r-- 1 nresa 197609 1909 Dec  1 14:31 KoolReport.subReport.js

koolreport_assets/417790547:
total 336
-rw-r--r-- 1 nresa 197609  88147 Dec  1 14:31 jquery.min.js
-rw-r--r-- 1 nresa 197609 253681 Dec  1 14:31 jquery-ui.min.js

So, this time, there was only 1 subfolder missing.

I wonder if the solution is to build this folder during deployment rather than trying to populate it at runtime. This would also be consistent with all other front-end packages, which are built using npm.

Regards Nick

Thank you David for your assistance. Having looked at this over the last several days, I think I've come to the conclusion that Koolreport is not going to work in this architecture. However, it's not the first software which struggled in the architecture. Even Laravel's own Spark package needed modifying to work there. I'm looking into migrating the project onto a more traditional LAMP stack using Laravel Forge, and feel the chances of success are much greater. Fingers crossed :-)

Hi David

Once again thank you very much for your help.

Since originally writing, I have investigated an alternative to KoolReport (Smart Reporting Engine - I found it to be far inferior to KoolReport and not really fit for purpose) and I have also run a proof of concept about migrating to Laravel Forge. The latter course will increase my costs but provides a number of advantages, not only that KoolReport seems to work in that environment, but also that I understand the technology far better, and that I can cut over to the new environment seamlessly from our existing implementation.

Good luck with investigating Vapor, and do keep me informed if you have any success!

Kind regards Nick