Deploy Application via Chef

After creating the Ruby on Rails application mentioned in my blog, the next task was to deploy the application to a hosted web server.

The traditional way would be to write rake tasks and trigger them manually or using a CI build/deploy. Well chef provides another easy solution to deploy an application. The recipe below performs all the tasks of deploying an application. The before_migrate script contains the tasks that need to be performed before the application kicks in. The migration_command is the final command that is run to mark deployment successful. deploy_revision is used to make sure that the recipe would only be executed once the git head changes in the repository from the last deployed version. symlink_before_migrate can be used to create symlinks to the yml files used in the configuring the application.

The deploy cookbook for a basic app looks like below

app_user="user"

deploy_dir="/opt/application_deploy"

user  app_user

directory "/home/#{app_user}/.ssh" do

mode "0700"

owner app_user

group app_user

end


cookbook_file "/home/#{app_user}/.ssh/deploy" do

source "deploy"

mode "0600"

owner app_user

group app_user

end


cookbook_file"/home/#{app_user}/.ssh/config" do

source "ssh_config"

mode "0644"

owner app_user

group app_user

end


directory deploy_dir do

recursive true

owner app_user

group app_user

mode "755"

end


%w{config log}.each do |dir|

directory "#{deploy_dir}/shared/#{dir}" do

owner app_user

group app_user

mode "755"

recursive true

end

end


gem_package "bundler"


cookbook_file "#{deploy_dir}/shared/config/database.yml" do

source "database.yml"

mode "0644"

owner app_user

group app_user

end

deploy_revision deploy_dir do

repo "<Git hub repository ssh url>"

environment "production"

revision "HEAD"

user app_user

symlink_before_migrate "config/database.yml" => "config/database.yml"

migration_command "bundle exec rails server -d -e production"

migrate true

action :deploy

restart_command "touch tmp/restart.txt"

before_migrate do

execute "bundle install" do

command "bundle install --path .bundle"

cwd  "#{release_path}"

user app_user

end


execute "Create db" do

command 'bundle exec rake db:create RAILS_ENV="production" '

cwd "#{release_path}"

user app_user

end


execute "Migrate db" do

command 'bundle exec rake db:migrate RAILS_ENV="production"'

cwd  "#{release_path}"

user app_user

end

end

end

Comments

Post a Comment

Popular posts from this blog

To DR or Not To DR

Image
Most organizations these days look at strategies and ways of implementing a "working" DR solution. Often a DR plan of action is a manual process based on multiple approvals at each level from Incident Management Teams to Product Ownership teams. What if there was a way to keep an active DR running where failure of a primary site would seamlessly transfer the traffic to the secondary site. In fact if the DR is active or warm then the only manual bit would be disabling the primary site via DNS. A few tips and tricks that would help in a simple implementation of a warm DR for an application hosted on AWS. AMI  Make sure that the AMIs are built across both the primary and secondary region.  The fastest way to build multi-region AMIs would be to use different builds for each region using the same configuration management code altering the "REGION" parameter each time. This would make the AMIs consistent and available in each region. PACKAGE REPOSITORY
Read more

High Availability NAT for AWS VPC with Multiple Private Subnets.

Image
VPCs have become the de-facto architectural choice when deploying enterprise applications. They are highly secure, keep your infrastructure logically separated which when combined with the power that AWS has to offer become highly available and robust. The one thing, however, that still feels like a point of failure are the NAT instances that need to be created for all private subnet outbound connectivity to the internet or any service that is external to the VPC. This brings us to create a sort of NAT failover mechanism. High Availability for Amazon VPC NAT Instances by Jinesh Varia offers a solution for a simple VPC that has active NATs per private subnet and each keeps pinging the other till one of them loses connectivity. The active NAT, at that moment, "takes over" the route for the failed NAT. An edge case to this solution is when you have private subnets per AZ and there is a loss of connectivity between AZs. We were faced with the same issue, which brought the t
Read more

Load Balancer with SSL offloading - nginx + HAProxy

Image
HAProxy and nginx can be configured together to work as an SSL offloader and a load balancer. Listed below are the steps to achieve the same on a centOS instance. Assume 192.168.1.1 and 192.168.1.2 running web servers on port 80 and 192.168.1.3 running haproxy on port 8181. Starting with HAPROXY set up. 1.  Install haproxy.        yum install -y haproxy 2.  Edit the haproxy configuration to update the backend web servers and keep it at the basic log level.     global   log 127.0.0.1   local2   chroot          /var/lib/haproxy   pidfile         /var/run/haproxy.pid   maxconn         4096   user            haproxy   group           haproxy   daemon   defaults                      mode            http   log             global   option          httplog   option          dontlognull   option          http-server-close   option          forwardfor except 127.0.0.0/8   option          redispatch   retries         3   timeout         http-request    20s   timeout        
Read more