I don't know how to use
node-red-contrib-smb to get file，pls help me....
I don't know how to use
Hi @GordonSu - it isn't a node I've ever used, but looking at it, I can see you can configure the node to do the operation 'Get File', along with the path of the file to get.
Unless someone responds who has used the node (but given its download stats, that may be unlikely), could you describe a bit more about what you've tried so far?
At the moment I am not even able to install the package:
root@node-red:~# npm install -g node-red-contrib-smb npm ERR! path git npm ERR! code ENOENT npm ERR! errno ENOENT npm ERR! syscall spawn git npm ERR! enoent Error while executing: npm ERR! enoent undefined ls-remote -h -t https://github.com/netsmarttech/node-smb2.git npm ERR! enoent npm ERR! enoent npm ERR! enoent spawn git ENOENT npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2019-05-31T14_54_27_878Z-debug.log
Does the server running node-red have internet access?
And normally we don't encourage people to install nodes globally. (drop the -g if you can)
root@node-red:~# npm install -g node-red-contrib-smb
also why are you running as root?
@Steve-Mcl : yes, it does. all the other packages can be easily installed.
@dceejay: you're right. Usually I use the "manage palette" install function from the editor. I just made a test with command line.
@zenofmud: also right. will be changed soon...
This means npm could not find the Git binary in your environment (probably not installed). If you check the node's
package.json, you'll see that one of its dependencies is linked to a git repository, and that's why git is needed there.
We're the developer of this node, we've let it like this at the time because of issues with the original smb library. There are other minor issues with this node we want to fix, so we can already check if we can change it back to the original npm dependency.
@gfcittolin I noticed you just released a new version (1.1.0).
Installation and the package in general is now working fine!
I am just reading text files from our server, but no issues for the moment.
Thanks a lot!!!!
You're welcome! I tried to improve the node's layout and documentation, hopefully making it easier to use. Beside of that, some bugs on specific configuration scenarios were fixed. Let me know if you find any other issue
For the moment seem to be running like a charm!
There is only one thing I don't understand: I have to specify a specific share folder in the config node. If I specify only the address seems not to work (see images). But maybe this is related to how our server is configured...
why mine always shows blue dot process only? anything wrong? something missed for nodejs I guess...