Where is my all flows are save in file-system.
8,788 views
Skip to first unread message
Rahul Kumar Prajapati
Apr 10, 2015, 6:38:23 AM4/10/15
to node...@googlegroups.com
Hi I want to view my flows in my file system.in which folder I can view my own created flows.
Nicholas O'Leary
Apr 10, 2015, 6:42:31 AM4/10/15
to Node-RED Mailing LIst
Hi Rahul,
when node-red starts up, it prints out what flow file it is using:
10 Apr 11:41:06 - [info] User Directory : /home/nol/.node-red
10 Apr 11:41:06 - [info] Flows file : /home/nol/.node-red/flows_noltop.json
By default, it uses flows_<hostname>.json inside your user directory (which, by default is $HOME/.node-red).
Nick
On 10 April 2015 at 11:38, Rahul Kumar Prajapati <ra...@bizician.com> wrote:
Hi I want to view my flows in my file system.in which folder I can view my own created flows.
--
http://nodered.org
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Rahul Kumar Prajapati
Apr 10, 2015, 7:25:32 AM4/10/15
to node...@googlegroups.com
Thanks Nicholas
mfeb
May 4, 2015, 11:04:57 AM5/4/15
to node...@googlegroups.com
Has this been discussed elsewhere?
I'm getting accustomed to this arrangement. It's a bit disconcerting at first, but makes sense with some use.
One thing some users must deal with is the change to hostname when changing locations (e.g., different hostname at home versus at work) and when working on different hosts (mac and linux). Easiest is to pick a host-name free name for the flows file and be done with it.
The other thing is managing separate "sheets", when changing between projects, prototypes, ... Again, that can be managed at the filesystem level, so keeping track of these separate files and starting node-red with the desired flow project file.
One thing that can be dangerous is to rely on the default flows file when managing, say, experimental clean flows files and the more built-out flows files. With multiple restarts and no explicit backups, it's possible to wipe out the built-out flows file (thank goodness for TimeMachine!).
One thing that can be a challenge is to "share" reusable (sub)flows among projects (flows files). Export-Import seems to be the best way, but ultimately it seems like the best way to reuse, say, function nodes is to convert them to node-red nodes. Flow subgraphs (and/or subflows)? - that's another challenge - how to share/reuse without having to maintain each copy.
I'm getting accustomed to this arrangement. It's a bit disconcerting at first, but makes sense with some use.
One thing some users must deal with is the change to hostname when changing locations (e.g., different hostname at home versus at work) and when working on different hosts (mac and linux). Easiest is to pick a host-name free name for the flows file and be done with it.
The other thing is managing separate "sheets", when changing between projects, prototypes, ... Again, that can be managed at the filesystem level, so keeping track of these separate files and starting node-red with the desired flow project file.
One thing that can be dangerous is to rely on the default flows file when managing, say, experimental clean flows files and the more built-out flows files. With multiple restarts and no explicit backups, it's possible to wipe out the built-out flows file (thank goodness for TimeMachine!).
One thing that can be a challenge is to "share" reusable (sub)flows among projects (flows files). Export-Import seems to be the best way, but ultimately it seems like the best way to reuse, say, function nodes is to convert them to node-red nodes. Flow subgraphs (and/or subflows)? - that's another challenge - how to share/reuse without having to maintain each copy.
Dave C-J
May 4, 2015, 11:37:35 AM5/4/15
to node...@googlegroups.com
Hi Mark,
The original thought behind including the hostname was to prevent accidental overwriting of a flow when you move it from one machine to another - so I can backup machines onto one and not have to worry.... - as you say the easy way "round" this is just start Node-RED with a flow flle parameter on all the boxes ..... node-red flow.json etc..
There should also be a one level backup called .{flowname}.backup - which is the previous version of the flow..
so eg flow_dcj.json should have a backup called .flow_dcj.json.backup (yes the . makes it hidden)
There is also the built in library for saving fragments of code / nodes / parts of flows - obviously this is local per machine - but is useful if you need to save work in progress and "neat routines" for use in other projects before exporting them elsewhere. Also of course you can link that directory to something like Dropbox and have it auto sync to other places.
Vimniky Luo
Nov 13, 2016, 10:02:24 PM11/13/16
to Node-RED
Hi ! Where's my exported node and flow?
Colin Law
Nov 14, 2016, 2:05:14 AM11/14/16
to node...@googlegroups.com
How are you exporting them? Tell us *exactly* what you do.
Colin
--
http://nodered.org
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/add99a1f-c9fe-4fcf-8d12-a862bb678964%40googlegroups.com.
Dave C-J
Nov 14, 2016, 3:55:06 AM11/14/16
to node...@googlegroups.com
when you start Node-RED the console will print the name and path of the flow file.
Usually it is in your .node-red directory called something like flows_{your_pc_name}.json
Reply all
Reply to author
Forward
0 new messages