Simple bash based deployment script

.env

# deploy to:
SERVER=server.com
APP=app_name
DEPLOY=/srv/$APP
ENVIRONMENT=production

# clone source from:
REPO=ssh://[email protected]/username/repo.git
BRANCH=master

README.md

Bash Deployment

• Copy deploy.sh to bin/deploy and mark it as executable
• Create an .env file with your config settings (see below)
• Make sure you have your ssh-config set up to forward your ssh keys.

Run bin/deploy!

Config Settings

Add these to an .env file:

 # deploy to:
 SERVER=server.com
 APP=app_name
 DEPLOY=/srv/$APP
 ENVIRONMENT=production
 
 # clone source from:
 REPO=ssh://[email protected]/username/repo.git
 BRANCH=master

Branches

If you want to deploy a branch, just call bin/deploy --rev=branch_name.

What's next?

This is really just a proof of concept. Extra flags could be added and more functions could be to come. But this proves how easy it is to start.

deploy.sh

#!/usr/bin/env bash

set -e

# get config settings
source .env

# process arguments
while test $# != 0; do
  case "$1" in
    --rev=*)
      REF="${1#--rev=}"
  esac
  shift
done

echo "Processing  deploy"
if [ -z "$REF" ]; then
  REMOTE_REF=origin/$BRANCH
else
  REMOTE_REF=origin/$REF
fi
  
scp .env $APP@$SERVER:$DEPLOY/.env

ssh $APP@$SERVER "sh -l -c 'cd $DEPLOY && \
                  git fetch origin && git reset --hard $REMOTE_REF && \
                  (git rev-parse HEAD > $DEPLOY/REVISION) && \
                  bin/bundle install --deployment --quiet --binstubs \
                          --without development test && \
                  bin/foreman run rake assets:precompile && \
                  bin/bluepill --no-privileged -c $DEPLOY/tmp restart'"

migrate.sh

#!/usr/bin/env bash

set -e

# get config settings
source .env

echo "Migrating database"
ssh $APP@$SERVER "sh -l -c 'cd $DEPLOY && \
                  bin/foreman run rake db:migrate'"

Looking good. If you add in some database migration handling it'd cover most deployment scenarios.

@mvandenbeuken Just updated it to be a bash script instead of a sh script and to use the .env file rather than specify its own settings.

By using the .env file (which we use already with foreman), I can now create a separate migrate script that uses the same settings.

Just added the migrate script

Moved to https://github.com/mm53bar/plow