refactor: streamline scripts

Author: themightychris

script/-check-docker-compose

@@ -0,0 +1,13 @@
+#!/bin/bash
+
+# script/bootstrap: Resolve all dependencies that the application requires to
+#                   run.
+
+set -e
+cd "$(dirname "$0")/.."
+
+
+if ! docker-compose ps -q app > /dev/null; then
+    echo "No server running yet, run ./script/server to launch"
+    exit 1
+fi

script/bootstrap

@@ -1,10 +1,26 @@
-# See https://github.com/github/scripts-to-rule-them-all
-#
-# script/bootstrap is used solely for fulfilling dependencies of the project.
-#
-# The goal is to make sure all required dependencies are installed.
+#!/bin/sh
 
-set -eu -o pipefail
-shopt -s failglob
+# script/bootstrap: Resolve all dependencies that the application requires to run.
 
-docker-compose pull
+set -e
+cd "$(dirname "$0")/.."
+
+
+echo
+echo "==> Verifying docker and docker-compose…"
+
+if ! [ -x "$(command -v docker)" ]; then
+    echo "Please install docker"
+    exit 1
+fi
+
+if ! [ -x "$(command -v docker-compose)" ]; then
+    echo "Please install docker-compose"
+    exit 1
+fi
+
+if ! docker info > /dev/null 2>&1; then
+    echo "Docker engine is not running, or your user does not have access to connect."
+    echo "Try starting Docker, adding your user to the docker group, or running this command with sudo"
+    exit 1
+fi

script/cibuild

@@ -1,16 +1,13 @@
-# See https://github.com/github/scripts-to-rule-them-all
-#
-# script/cibuild is used for your continuous integration server. 
-# This script is typically only called from your CI server.
-#
-# You should set up any specific things for your environment here 
-# before your tests are run. Your test are run simply by calling script/test.
+#!/bin/sh
 
-set -eu -o pipefail
-shopt -s failglob
+# script/cibuild: Build production deployment artifact
 
-scripts/test
+set -e
+cd "$(dirname "$0")/.."
 
-docker build -t upenn/chime .
 
-# FUTURE - should the container be pushed anywhere?
+script/bootstrap
+
+echo
+echo "==> Building and tagging container…"
+docker build -t codeforphilly/chime .

script/console

@@ -1,15 +1,29 @@
-# See https://github.com/github/scripts-to-rule-them-all
-# 
-# script/server is used to start the application.
-#
-# For a web application, this might start up any extra processes
-# that the application requires to run in addition to itself.
-#
-# script/update should be called ahead of any application booting 
-# to ensure that the application is up to date and can run appropriately.
+#!/bin/sh
 
+# script/server: Launch the application and any extra required processes
+#                locally.
 
-set -eu -o pipefail
-shopt -s failglob
+set -e
+cd "$(dirname "$0")/.."
 
-docker-compose up -d
+
+script/bootstrap
+
+if [ ! -f ".env" ]; then
+    echo
+    echo "==> Initializing .env…"
+    cp .env.example .env
+fi
+
+echo
+echo "==> Loading .env…"
+set -o allexport; source .env; set +o allexport
+
+echo
+echo "==> Starting containers with docker-compose…"
+docker-compose up -d --build
+
+echo
+echo "==> App is now ready to go!"
+echo "    *Open http://localhost:${PORT}"
+echo

script/server

@@ -1,18 +1,14 @@
-# See https://github.com/github/scripts-to-rule-them-all
-#
-# script/update is used to update the project after a fresh pull.
-#
-# If you have not worked on the project for a while, 
-# running script/update after a pull will ensure that everything 
-# inside the project is up to date and ready to work.
-#
-# Typically, script/bootstrap is run inside this script.
-# This is also a good opportunity to run database migrations 
-# or any other things required to get the state of the app into 
-# shape for the current version that is checked out.
+#!/bin/sh
 
-set -eu -o pipefail
-shopt -s failglob
+# script/update: Update application to run for its current checkout.
 
-docker-compose down
-scripts/bootstrap
+set -e
+cd "$(dirname "$0")/.."
+
+
+script/bootstrap
+script/-check-docker-compose
+
+echo
+echo "==> Rebuilding containers…"
+docker-compose up -d --build