Nodered Permission denied from source code
- I cloned the git repo and installed openflow locally. Now the problem is I can't see nodered link on openflow nav bar, but when I create a nodered instance from openflow url with Nodered endpoint (http://localhost.openrpa.dk/#/Nodered) getting connect ECONNREFUSED 127.0.0.1:8080 Error from the openflow and getting permission denied from the openflownodered. PFA of error logs FYI
- I have some more doubts I'm curious about learn how you are managing multi tenant mode for openflownodered instance.
3)Some more questions in queue....
Thanks in Advance,
The nodered tab is only for running inside docker or kubernetes
So Can't we run nodered locally?
yes you can. Either run in from visual code, install is as an npm package, or start a docker instance where you set the correct envoriment variables your self.
I tried from the source code but nodered is failed to run locally. and also tried from npm package both openflow and opeflownodered failed to install. is there any way to run only nodered from the source code please.
So both me and all my happy customers can make it work just fine both as npm and distriubted by docker, so maybe the fault is not in the code/platform ? But if you feel you found a bug or a problem, feel free to report a prober re-producable way to show it, submit a pull request that fixes it, or sign up for commercial support if you need training and support.
No, the whole idear is to have nodered use the features offered by Openflow. If all you want, is nodered, then simply install nodered as an npm package. And then you can maybe use pm2 or other packages to run it as a service if that is also needed.
My implementaion of nodered DOES support running "offline" but only after having initialy been started and connected to openflow at least once. And only for a limited time ( until you run out of diskspace )
If you need to run multiple nodered decoupled for longer periods of time, have a look at running multiple openflow instances in mesh topologies.