This content has been written a long time ago. As such, it might not reflect my current thoughts anymore. I keep this page online because it might still contain valid information.
Deploying With GitClermont-Fd Area, France
Yeah, I know yet another blog post on this topic. The main difference with others is that I wrote it myself, and it’s quite up to date :p
When you need to deploy a simple web application on a server, like this
blog for instance, there is no need to use Capistrano or Fabric.
It’s just about copying a set of files, so you could rely on
scp… But it’s not fun!
Actually, you just need to rely on Git, assuming you are using it.
The first step is to configure your local repository by adding a new remote:
git remote add -t master production ssh://<server>/path/to/project_prod
-t <branch> option allows you to track a given branch instead of all branches.
You can add more remotes if you want like a
git remote add testing ssh://<server>/path/to/project_test
To deploy the application in production, run:
git push production
And, to deploy it in a testing environment, run:
git push testing <branch>
Now, you can push your code on your server, but it won’t deploy your changes at the moment.
So let’s configuring Git. First, add the following lines to your
[receive] denyCurrentBranch = false
It allows to push code on the current branch, it’s important to deploy your new changes. Old Git versions don’t need to set this parameter by the way.
Then, enable a
post-receive hook with the following content:
#!/usr/bin/env bash SUBJECT="Deploy successful" BODY="You've successfully deployed the branch:" while read oldrev newrev ref do branch=`echo $ref | cut -d/ -f3` if [ "$branch" ] ; then cd .. env -i git checkout $branch env -i git reset --hard EMAIL=`env -i git log -1 --format=format:%ae HEAD` BODY="$BODY $branch." echo "$BODY" | mail -s "$SUBJECT" "$EMAIL" fi done
This script updates the working tree after changes have been pushed, and send an email to the last committer. Keep in mind that it always deploys the last branch you push.
The important part is:
cd .. env -i git checkout $branch env -i git reset --hard
Feel free to decorate these three lines as you wish.
In a production environment, or because you are using a
Git Branching Model,
you should modify the previous code as below.
It ensures to always deploy the
if [ "$branch" == "master" ] ; then cd .. env -i git reset --hard // Send an email fi
You’re done, each time you’ll run a
git push production, you’ll deploy your application in production.
Easy. Fast. Powerful.