Files
projectr/bin/site_deploy
T
lukas bb033b58cc Make the revision param for deployments optional
The deployment script now uses the current revision of the set branch in this case. Does not work together with a custom value of $CONFIG_HASH_LENGTH though.
2015-09-11 23:24:43 +02:00

28 lines
925 B
Bash
Executable File

#!/bin/bash
########################################################################
# 2014-09-07 Lukas Bestle mail@lukasbestle.com
########################################################################
# Clones the repository of a site from the server, runs the script
# .postdeploy.sh in the repository (if existing) and links the version
# as current.
#
# Usage: site_deploy <site> [<revision>]
#
# <site> Name of the site (directory in ~/web/sites/)
# <revision> SHA-1 commit hash of the revision to checkout
# Defaults to the latest commit on the set branch
########################################################################
site="$1"
revision="$2"
if [[ -z "$site" ]]; then
# Print help
echo -e "\033[1mUsage:\033[0m \033[34msite_deploy\033[0m <site> [<revision>]"
exit 1
fi
# Delegate to project_deploy
project_deploy "$HOME/web/sites/$site" "$revision"
exit $?