Hi, I’ve setup standalone server for testing on my machine, and replicated my cloud environment, which include nodejs scripts in the web/scripts area. However, when I call one, I get a 400 error, with “No script runner is available”. Is there something else I must do to get this working?
Hi Paul!
nodejs scripts execution not supported in standalone version of Backendless.
In your local environment you can install nodejs and execute scripts in the same way like
on Backendless cloud.
I didn’t install anything on the cloud version, I used files, i.e. in the web/scripts area.
I need this ability to use the platform for testing locally, or deploying myself.
Hi Paul,
Since everything is on a machine you control, what stops you from starting your own, local node.js process with any script you need?
Regards,
Mark
Because I wouldn’t be running within the bounds of the Backendless environment, i.e. I wouldn’t have an exact replica of the cloud platform, on my local machine, for testing. Or isn’t nodejs scripts in the web area, calling backendless APIs, a standard part of your platform, like it is in the cloud?
That is, I was expecting to download the stand-alone, put all of my code into it exactly as it is in the cloud version, do my testing, prove everything works, then push it back to the cloud for “production”.
The main reason I’m doing this, is that testing with nodejs scripts in the cloud version is very difficult. So I wrote a test harness locally, which replicates the API, and works, but is not code compatible with my scripts, i.e. I can’t just push it to the cloud. So I thought the best way to debug / test, was to download the stand-alone, get it working, then be confident that when I push to the cloud (and test), it will work.
I understand, although the Standalone version is identical to the cloud version, there are 2 elements not included: media server and node.js container for the hosting scripts. This may change in the future though.