Skip to content

rdsubhas/ruby-deploy-kickstart

Repository files navigation

Ruby (and Rails) Deployment Kickstart

A template for deploying Ruby and Rails applications, with automation support for Ansible, Docker and Vagrant. Copy this over to your project, and modify to fit.

Read the accompanying blog post for more details.

Structure

NOTE: The files will look overwhelming at first, because they contain Vagrant, Ansible and Docker. You don't need everything. If you don't want Docker, get rid of Docker-related files. Similarly, if you don't want Ansible or Vagrant, get rid of those files.

  • Core application files are: myapp.rb, myapp.ru, myjobs.rb
  • Core supporting files are: .env, Procfile, Gemfile*, provisioning/roles/myapp/files/.env
    • The default .env file is suitable for development mode
    • In production, it is overwritten with provisioning/roles/myapp/files/.env
  • Docker: .dockerignore, Dockerfile
  • Vagrant: Vagrantfile
  • Ansible: provisioning/*

Development

  • Install Vagrant and VirtualBox
    • Preferably, install vagrant-cachier, vagrant-exec and vagrant-faster plugins for a faster development experience
  • Run: vagrant up
  • Run: vagrant ssh > cd /vagrant > foreman start
    • Or if you have installed vagrant-exec, simply run vagrant exec foreman start
  • Go to localhost:3000, it will echo you a message with development configurations

Production using Ansible

Supports only Debian and Ubuntu for now

Testing:

  • Stop everything else: vagrant halt
  • Start the Prod VM: vagrant up prod
  • Go to localhost:3000, it will echo you the same message with production configuration

Actual Deployment:

  • Go to provisioning folder
  • Edit prod_inventory and update your production server name
  • Run: ansible-playbook -i prod_inventory -u <username> -vvv prod.yml

Production using Docker

Supports any OS that can run Docker, not limited to Debian/Ubuntu

Testing:

  • Stop everything else: vagrant halt
  • Start the Docker VM: vagrant up docker
  • Go to localhost:3000, it will echo you the same message with production configuration, except things are running using Docker now

Actual Deployment:

  • Check the Docker section in Vagrantfile for the build and run commands
  • A full discussion of Docker is beyond the scope of this, but the gist is:
    • Build the Docker image (can be done locally or on the server)
    • Push it to a registry (not needed if you built on the server)
    • Run it in the server
    • For exact commands, check the Docker section in Vagrantfile

In case of errors

  • Destroy the VMs: vagrant destroy
  • Start whatever you want up again

Using it in your project:

  • Add Foreman and rails_12factor to your Gemfile
  • Copy necessary files (provisioning, .env, Procfile, Vagrantfile, Dockerfile) from here to your project
  • Modify them to fit, especially:
    • Procfile commands
    • roles/myapp/
  • Encrypt production configuration (using git-crypt, ansible vault, or anything else)
    • provisioning/roles/myapp/files should be encrypted

About

Ruby (and Rails) deployment kickstart with dotEnv, Foreman, Ansible, Docker and Vagrant

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages