I assume you mean the folder being deleted? Well, you would need to understand what caused it. Certainly just using npm to install a new version of Node-RED doesn't do that and I don't believe running Dave's script would either.
Ultimately though, while Node-RED is amazingly stable and robust, it is still just a collection of code and so can go wrong easily enough.
Backups are your one and only friend.
I have 3 scripts. a Daily backup, a weekly backup and a monthly backup. The 1st keeps 7 daily backups, the 2nd 5 weekly backups, and the 3rd 12 monthly backups. They currently take up 320M & I've shared the scripts previously, they use rsync to keep things efficient.
You need to set an initial breakpoint in settings.js if I remember.
Sadly: YES, it did. (Not the first time, that's why I've made a backup before that.)
If I develop a component, and change the JSON file, it seems it does not match with original on the server (since it is not stable, so It's not merged / uploaded there yet.)
So somehow it gets completely deleted.
IMHO NPM should not be trusted.
How do I do that?
Will it help with the "32 bit ... " error above? (I don't think it has anything to with it does it?)
Wow! That's new to me! This could be it...
But I never used the keyword node to start node-red, only node-red-start.
If I simply type node into a SSH terminal, it starts some kind of editor.
Also I don't know what directory this ./data is?
Almost all Raspberry Pi systems are 32 bit by default! That's why it's interesting, why nobody is complaining about this error...
The GitHub ticket has been made read-only too.
I’ll chime in that I once had all my flows blanked out (tabs were still there but all were empty) this was also on a pi. Wasn’t able to pin what exactly caused it, I was probably doing something weird, but the lesson was learned - there’s no replacement for regular backups.
Well, if you want to get into deep debugging, you need to lift up the covers and peer within a little
I never run Node-RED as a global install, I always run it as a local install with the userDir folder within the folder that Node-RED is installed to. See the alternate installer repo on my GitHub for details.
Depending on how you have installed Node-RED, both the location of the RED.js file and the location of your userDir may be different.
ARMv7 and below are 32-bit. AMRv8 introduces the 64-bit instruction set. Type the command lshw to see what you have.
Typically Pi3 and below run 32-bit and Pi4 runs 64-bit I believe but I think that the Pi3 can run 64-bit (I've not tested it).
That's because the repository that it refers to is no longer in use and has been deprecated.
THe "error" is only a warning anyway so debugging should still work.
I think that this statement is not correct. This has nothing to do with npm.