Skip to content

Commit 12727ed

Browse files
juggledaddceejay
authored andcommitted
added explaination of [flow.json] in "Command-line usage" section (#80)
Added an explaination of how you can use the [flow.json] option to keep different undertakings in seperate files.
1 parent 27b18ea commit 12727ed

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

docs/getting-started/running.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,9 +52,13 @@ You can now create your [first flow](first-flow).
5252
-u, --userDir DIR use specified user directory
5353
-v enable verbose output
5454
-?, --help show usage
55+
[flows.json] name of the data file you want to work with. Using different names,
56+
such as greenhouse.json or robot.json, you can separate different
57+
undertakings you are working on. If you don't specify a name, it
58+
defaults to flows_xxxxxxxx.json where xxxxxxxx is your servername.
5559

5660
----
57-
61+
5862
#### Running from a local install - Linux & Mac OS X
5963

6064
The `node-red` command can still be accessed even if Node-RED hasn't been installed

0 commit comments

Comments
 (0)