taler-deployment

commit d545c73fcf80611dd8bae741d4f4253b96dd0506
parent e08e058f8640e3dad7864cd7c5554be32d90c1a5
Author: Marcello Stanisci <stanisci.m@gmail.com>
Date:   Sat,  8 Jun 2019 19:54:10 +0200

dependencies.

the "shared-data" script only starts if config was first generated.

Diffstat:
M
bin/taler-deployment-shared-data
 | 
14
++++++++++++--

1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/bin/taler-deployment-shared-data b/bin/taler-deployment-shared-data
@@ -21,9 +21,14 @@ if ! test -e $SHARED_DATA; then
   exit 1
 fi
 
+if ! test -e $HOME/.conf/taler.conf; then
+  echo "Please generate config first (taler-deployment-config-generate)."
+  exit 1
+fi
+
 # Check if shared-data/ is clean.
-if ls -L -1 $SHARED_DATA | grep -q [a-zA-Z]; then
-  echo "$SHARED_DATA not empty, exiting"
+if test -e $SHARED_DATA/hier.lock; then
+  echo "$SHARED_DATA locked, exiting"
   exit 0
 fi
 
@@ -63,6 +68,11 @@ declare -A TALER_DIRS=(
 )
 
 for dir in ${TALER_DIRS[@]}; do
+
+  ##
+  # Ineffective for exchange's and auditor's privs paths
+  # as those were created when the configuration was generated
+  # (recall: this script is very dependent on taler.conf!)
   mkdir -p $dir
 done