README updates

README.md

@@ -98,6 +98,38 @@ There are [several examples][1] designed to test the fault tolerance of forever.
   $ forever -m 5 examples/error-on-timer.js
 ```
 
+### JSON Configuration Files
+
+In addition to passing forever the path to a script (along with accompanying options, described above), you may also pass forever the path to a JSON file, in which these options are defined. For example, consider an application with the following file structure:
+
+```
+.
+├── forever
+│   └── development.json
+└── index.js
+
+// forever/development.json
+{
+    "uid": "app",
+    "append": true,
+    "watch": true,
+    "script": "index.js",
+    "sourceDir": "/home/myuser/app"
+}
+```
+
+This application could be started with forever, as shown below:
+
+``` bash
+$ forever start ./forever/development.json
+```
+
+Absolute paths to such configuration files are also supported:
+
+``` bash
+$ forever start /home/myuser/app/forever/development.json
+```
+
 ### Using In Your Code
 The forever module exposes some useful methods to use in your code. Each method returns an instance of an EventEmitter which emits when complete. See the [forever cli commands][2] for sample usage.