Arweave Should Not Build Before Being Stopped

This commit fixes an issue related to `./bin/stop` script and
`./bin/arweave.env`. When stopping Arweave application in
dev environment, a full release is always created. It is not
clean and could probably leads to errors (even if was not the
case previously).

If `SKIP_BUILD` variable is defined then arweave is not
compiled.

Author: humaite

bin/arweave.env

@@ -18,7 +18,13 @@ else
     # extended start script to run from our current directory (which is necessary for relative
     # paths to work correctly and not be relative to the rebar3 _build release directory)
     echo Building dependencies for target ${ARWEAVE_BUILD_TARGET:-default}...
-    (cd ${PARENT_DIR} && ./ar-rebar3 ${ARWEAVE_BUILD_TARGET:-default} release)
+
+    # sometimes, arweave does not to be build, for example
+    # when someone is stopping a node.
+    if ! [ "${SKIP_BUILD}" ]; then
+        (cd ${PARENT_DIR} && ./ar-rebar3 ${ARWEAVE_BUILD_TARGET:-default} release)
+    fi
+
     export ARWEAVE="${SCRIPT_DIR}/arweave-dev"
     export ARWEAVE_COMMAND="console"
 fi

bin/start

@@ -3,6 +3,7 @@
 set -e
 
 SCRIPT_DIR="$(dirname "$0")"
+SCRIPT_ACTION="start"
 
 # Sets $ARWEAVE and $ARWEAVE_* variables
 source $SCRIPT_DIR/arweave.env

bin/stop

@@ -3,8 +3,10 @@
 set -e
 
 SCRIPT_DIR="$(dirname "$0")"
+SCRIPT_ACTION="stop"
 
 # Sets $ARWEAVE and $ARWEAVE_* variables
+SKIP_BUILD=yes
 source $SCRIPT_DIR/arweave.env
 
-$ARWEAVE stop
+$ARWEAVE stop