start.sh

#!/bin/bash

# didn't want to create a custom start script, but docker and webpack-dev-server + the custom hazel setup requires it.
# things have to orchestrated in a specific sequence that I couldn't perform with npm or docker

IMPORT_DATA=""
IMPORT_IMAGES=""
LOG="./devserver-startup.log"

rm ${LOG};
touch ${LOG};

# trap errors
trap 'error ${LINENO}' ERR
error() {
  msg="Error on or near line $1 - check ${LOG} for more";
  echo ${msg};
  echo "Stopping server..."
  docker compose down;
  exit 1;
}

# trap ctrl-c and call ctrl_c()
trap ctrl_c INT
function ctrl_c() {
  echo "Stopping server..."
  docker compose down;
  exit 0;
}

# accept user input for conditional steps
read -r -p "Do you want to import fresh data? (takes 3-4 min) [y/N] " response
if [[ "$response" =~ ^(yes|y|Y)$ ]];
  then
    IMPORT_DATA="Y"
 fi

 read -r -p "Do you want to update images?  (takes 4-5 min, or 15-20 min if it's the first time) [y/N] " response
if [[ "$response" =~ ^(yes|y|Y)$ ]];
  then
    IMPORT_IMAGES="Y"
 fi

# watch log until all containers are completely
docker compose up --wait -d 2>&1 | tee -a ${LOG}

# if requested, sync data
if [[ "${IMPORT_DATA}" == "Y" ]];
  then
    sleep 5
    docker exec -i ${APP_HOST} sh -c 'exec /project/bin/sync_db.sh'
fi

# if requested, sync images
if [[ "${IMPORT_IMAGES}" == "Y" ]];
  then
    sleep 5
    docker exec -i ${APP_HOST} sh -c 'exec /project/bin/sync_images.sh'
fi

# link dev hazel.config into cgi-bin
docker exec -i ${APP_HOST} sh -c 'ln -sf /project/config/hazel.config /project/cgi-bin/'
docker exec -i ${APP_HOST} sh -c 'ln -sf /project/config/hazel.config /project/bin/'

# install any new npm packages
echo "installing any new npm packages..."
npm install --legacy-peer-deps >> ${LOG} 2>&1

# run webpack-dev-server
echo "Starting webpack-dev-server on ${DEVSERVER_HOST}, please wait..."
NODE_ENV=development WEB_HOST=${WEB_HOST} node_modules/.bin/webpack serve --mode development --config config/webpack.config.js