Effective Rails Deployment01 Apr 2016
Capistrano has been an excellent tool for years to deploy simple or multi-stage complex applications to remote servers. However the rise of PASS like Heroku, Dokku, I got in mind to use some automatic orchestration framework.
I looked over Chef, Puppet, SaltStack and Ansible on a weekend and decided to go with ansible since it looked easiest to get hands dirty and have great documentation. After some initial hicups I was able to deploy some of our inhouse applications on EC2 and introduced it to my coworkers at codecrux.
Since then, we use ansible to configure and manage remote server, and also configure our local development environment running on top of Virtualbox with vagrant.
Ansible uses YAML for configuration and for actual commands it has less flexibility compared to capistrano which uses Ruby DSL, but at the same time helps you to keep your playbooks simple. ansible also extremely good with orchestration and rolling deployments. We were able to keep a homogenous command set and duplicate most of Capistrano’s features in very small amount of code.
Let’s take an example to deploy lobster.rs. Here is how we did it -
First of all you need to define required variables in a yaml file for ansible to pick them up.
You should also define your remote host in ansible inventory/host file like
[production] lobsters.dev ## replace with your domain name
Now when we have configuration we can create the actual playbook for doing capistrano-style deployments. Create
Once everything is set up, you can run the following command to deploy:
ansible-playbook -u railsbox -i production deploy.yml