#!/bin/bash
-# this config file provides the default values for the variables used in our site management scripts.
+# provides the default values for the variables used in our site management scripts.
+
+# config files for site avenger apps usually override nothing, since we
+# auto-construct the app name and domain.
+# if they do need to override anything, they can just specify replacement
+# values for the variables in this file.
####
####
-# config files for site avenger apps usually override nothing, since we
-# auto-construct the app name and domain. but if they do need to override
-# anything, it will be below this point in the file.
-# the derived config file should include the basic configs like so:
-#
-# source "$WORKDIR/config/default.app"
-
-####
-
# deployment information for the application / site.
export APPLICATION_NAME="${app_dirname}"
# a special override for the mapsdemo site, which we want to put in as
# a subdomain of the cakelampvm domain.
-source "$WORKDIR/config/default.app"
-
export DOMAIN_NAME="${APPLICATION_NAME}.cakelampvm.com"
+echo "*** overrode domain name as: $DOMAIN_NAME"
+
export SITE_MANAGEMENT_CONFIG_FILE
if [ -z "$SITE_MANAGEMENT_CONFIG_FILE" ]; then
SITE_MANAGEMENT_CONFIG_FILE="$WORKDIR/config/default.app"
+ echo "Site management config file was not set. Using default:"
+ echo " $SITE_MANAGEMENT_CONFIG_FILE"
fi
# load in at least the default version to get us moving.
echo "Application folder is: $app_dirname"
local configfile="$WORKDIR/config/${app_dirname}.app"
+echo hoping config file would be: $configfile
if [ ! -f "$configfile" ]; then
# this is not a good config file. we can't auto-guess the config.
echo -e "
# reinitialize some variables based on the app name.
else
# they gave us a valid config file. let's try using it.
- SITE_MANAGEMENT_CONFIG_FILE="$configfile"
+ export SITE_MANAGEMENT_CONFIG_FILE="$configfile"
fi
# try to load the config.