Hi Kuema!!
I need to install node-red on an industrial PC not connected to the internet.
If I'm not too invasive, could you tell me which procedure you use?
Thanks in advance!
Mainly this one using a thumb drive:
Just sweep other that thread and some other linked posts, I think I described it in different posts. Been a while. 
No offense, but if you have specific questions for your use case, you should open a new thread where everyone can participate and benefit from.
1 Like
Ok you are right, just two questions.
You installed the same version of node.js and then copied and pasted npm into %appdata% and the .node-red right?
And you have used a windows 7 configuration on other windows like 10 or enterprise?
You would help me a lot if you answer me
We just have the node.exe on the target machine. The node versions (12, 14...) and OS architectures (win32, linux; 32 or 64-bit) have to match, of course, if you have packages with native code.
I think anything equal or above Windows 7 should work.
Also, we run multiple instances and pass the workspace on start with -u, no default paths here. (there are forum threads about that as well, like here: Multiple node red instances - #2 by kuema)
For workspace updates, I just remove the old node_modules on the target and move the one from my development machine in. Same goes for your Node-RED, we have that in a separate directory.
1 Like
Ok I understand.
how do you get only node.exe?
and how do you get this structure?
.
├── apps
│ ├── node-red -> node-red_1.0
│ ├── node-red_0.19
│ ├── node-red_0.20
│ └── node-red_1.0
└── workspaces
├── node-red-controller
│ ├── flows_cred.json
│ ├── flows.json
│ ├── lib
│ ├── node_modules
│ ├── package.json
│ ├── package-lock.json
│ └── settings.js
├── node-red-dashboard
│ ├── flows_cred.json
│ ├── flows.json
│ ├── lib
│ ├── node_modules
│ ├── package.json
│ ├── package-lock.json
│ ├── settings.js
│ └── static
├── node-red-telegram
│ ├── flows_cred.json
│ ├── flows.json
│ ├── lib
│ ├── node_modules
│ ├── package.json
│ ├── package-lock.json
│ └── settings.js
└── node-red-test
├── flows_cred.json
├── flows.json
├── lib
├── package.json
└── settings.js
I have this:
.
└── .node-red
├── lib
├── node_modules
├── flows.json
├── config.json
├── package.json
├── package-lock.json
└── settings.js
You have to create the directories yourself... or any other structure satisfying your use case, it's not fixed.
You can download the node.exe separately from the NodeJS site: Download | Node.js
I'm sorry, but I can't give personal support, my time is very limited. I'd rather have you open a public thread where everyone can participate, if you have any further issues for your use case. That way, others can benefit from the discussion as well. There are many users having similar use cases like this. 
(If you agree, I can convert this conversation into a public thread.)
1 Like
it's ok for me, it's good share.
I'm not sure where to put the node.exe
On our production systems with keep everything in one directory structure for the project, including all required software. The advantage is, you can make quick backups of the whole runtime including all dependencies and project configs.
But it depends on your software stack if that is an option.
Is there a guide on how to do this? I can't find it
That's how I do it in my day job on our customer's systems running our software (mainly Windows systems), most of them have no Internet access, only remote access (RDP, VNC, ...) via VPN.
There is no guide or out-of-the-box solution to this. You have to find a solution that fits your needs, customer requirements and specific use case. There are many approaches to this. Many pointers and hints of what is possible are already here on the forum and the posts I mentioned.
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
