Change directions on configuring directories

Update README
Update config.example.json

README.md

@@ -44,9 +44,7 @@ npm install
 Copy the config/config.example.json to config/config.local.json.  
 Use the config/config.js for documentation and further examples.  
 
-**`outcomes.dir`** Configure this value. This needs to be a directory of your choosing that both the orchestrator and app-scanner containers use. The `outcomes.dir` value should be the same as the testers `emissary.report.dir` and `results.dir` value. The directory you choose and configure needs group `rwx` permissions applied to it because the orchestrator and tester containers share the same group, they also read, write and delete outcome files within this directory.
-
 **`testerFeedbackComms.medium`** Long Polling `lp` is supported in both `local` and `cloud` environments. Server Sent Events `sse` is only supported in the `local` environment due to AWS limitations. Both `lp` and `sse` are real-time. Both implementations have their pros and cons.
 
-See the CLI documentation for further details around this value.
+See the [CLI documentation](https://github.com/purpleteam-labs/purpleteam#configure) for further details around this value.
 

config/config.example.json

@@ -20,7 +20,7 @@
     }
   },
   "outcomes": {
-    "dir": "</absolute-path-to/purpleteam/outcomes/>"
+    "dir": "/var/log/purpleteam/outcomes/"
   },
   "testerFeedbackComms": {
     "medium": "lp"

config/config.js

@@ -126,7 +126,7 @@ const schema = {
   },
   outcomes: {
     dir: {
-      doc: 'The directory that stores Tester results and Emissary reports. This directory needs group rwx permissions.',
+      doc: 'The directory that stores Tester results and Emissary reports.',
       format: String,
       default: '/var/log/purpleteam/outcomes/'
     },