The submodule is a leftover from when this project was intended to work as a series of microservices. It was meant to provide common functionality to the builds for every microservice. That's no longer the case, and the submodule is a pain-point both in on-boarding new developers and running the Docker build.
30 lines
789 B
Plaintext
30 lines
789 B
Plaintext
# run_bootstrap: Install application dependencies
|
|
|
|
# Load bootstrap functions
|
|
source ./script/include/bootstrap_functions.inc.sh
|
|
|
|
## Set option defaults
|
|
# If PIPENV_INSTALL_FLAGS is not set, give it the default value of "--dev"
|
|
if [ -z "${PIPENV_INSTALL_FLAGS+is_set}" ]; then
|
|
PIPENV_INSTALL_FLAGS="--dev"
|
|
fi
|
|
|
|
# If this is a CI build, only use the latest lock file for dep install
|
|
if [ "${CIBUILD}" = "true" ] || [ "${FLASK_ENV}" = "ci" ]; then
|
|
PIPENV_INSTALL_FLAGS+=" --ignore-pipfile"
|
|
fi
|
|
|
|
## Main
|
|
if [ "${INSTALL_PYTHON_PACKAGES}" = "true" ]; then
|
|
install_python_packages "${PIPENV_INSTALL_FLAGS}"
|
|
pipenv clean --verbose
|
|
fi
|
|
|
|
if [ "${INSTALL_NODE_PACKAGES}" = "true" ]; then
|
|
install_node_packages
|
|
fi
|
|
|
|
if [ -n "${COMPILE_SASS_CMD}" ]; then
|
|
run_command "${COMPILE_SASS_CMD}"
|
|
fi
|