From 949159327cc34863078495d240430f5977704ee4 Mon Sep 17 00:00:00 2001 From: Dave Conway-Jones Date: Tue, 28 Feb 2017 14:37:57 +0000 Subject: [PATCH] change user-Home to userDir to be same as existing settings convention --- Design:-Version-Control.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Design:-Version-Control.md b/Design:-Version-Control.md index 2906361..367882f 100644 --- a/Design:-Version-Control.md +++ b/Design:-Version-Control.md @@ -138,7 +138,7 @@ Quick mock-up: By default, the `localfilesystem` implementation should be entirely file based. - the base flow/credential files remain unchanged to how they work today - - a new directory structure is created alongside the flow file: + - a new directory structure is created alongside the flow files in the : my-flows.json my-flows_cred.json @@ -165,7 +165,7 @@ need to be exposed. that allows it to be maintained externally (eg GitHub). - User provides **flow file name**, eg `my-flows.json` - as they can today - - Node-RED uses a repository under `/my-flows` - creating it if needed + - Node-RED uses a repository under `/my-flows` - creating it if needed - Node-RED stores `my-flows.json` and `my-flows_cred.json` under that directory 2. a user wants to maintain a repo that contains more then just the flow files. @@ -174,7 +174,7 @@ need to be exposed. relative path within the repo. - If it is a local repo, Node-RED uses that repo directly. A user could configure a post-commit hook to handle pushing updates remotely. - - Otherwise, Node-RED clones that repo under `/.flows` and uses that, + - Otherwise, Node-RED clones that repo under `/.flows` and uses that, ensuring to do `git push` back to the origin - The user should be able to provide authentication settings for the git repo via settings - or by well-defined environment variables.