Add helper scripts for running from source, and document them.

Bouncer.sh

@@ -0,0 +1,10 @@
+#!/bin/sh
+#
+# Run the EDDN Bouncer from source
+
+set -e
+
+# Need to be in the src directory, relative to this script
+cd "$(dirname $0)/src" 
+# And we invoke the *module*, not the script by filename.
+python -m eddn.Bouncer $@

Gateway.sh

@@ -0,0 +1,10 @@
+#!/bin/sh
+#
+# Run the EDDN Gateway from source
+
+set -e
+
+# Need to be in the src directory, relative to this script
+cd "$(dirname $0)/src" 
+# And we invoke the *module*, not the script by filename.
+python -m eddn.Gateway $@

Monitor.sh

@@ -0,0 +1,10 @@
+#!/bin/sh
+#
+# Run the EDDN Monitor from source
+
+set -e
+
+# Need to be in the src directory, relative to this script
+cd "$(dirname $0)/src" 
+# And we invoke the *module*, not the script by filename.
+python -m eddn.Monitor $@

Relay.sh

@@ -0,0 +1,10 @@
+#!/bin/sh
+#
+# Run the EDDN Relay from source
+
+set -e
+
+# Need to be in the src directory, relative to this script
+cd "$(dirname $0)/src" 
+# And we invoke the *module*, not the script by filename.
+python -m eddn.Relay $@

docs/Running-this-software.md

@@ -387,15 +387,20 @@ You have some choices for how to run the application components:
 
 ## Running scripts from source
 If you are just testing out code changes then you can choose to run
-this application directly from the source:
+this application directly from the source.  To do so you need to reference
+the correct module with `-m` rather than specifying the file directly:
 
-```
+```sh
 cd <eddn files>/src
 python -m eddn.Gateway --config <full path to config.json>
 ```
+If running in an environment with a POSIX 'Bourne' shell then there are
+helper scripts:
 
-Check the `systemd/eddn_<environment>_config` files for the location of
+```sh
-the logs directory.
+cd <eddn files>
+./Gateway.sh --config <full path to config.json>
+```
 
 ## Running from installation
 Otherwise you will want to  utilise the `setup.py` file to build and