Deploying Ruby on Rails applications on Production Servers
This talk guides Ruby on Rails Developers on what they should think about when designing ,developing and deploying a web application on production servers such as Google Compute Engine, Amazon EC2, Digital Ocean, Linode or Rackspace Servers
community ❖ Can be used with other languages as well ❖ Organises operative directions in files known as recipes ❖ Not just userful with deployment, you can use it to build servers, install applications, maintenance and monitoring ❖ Great documentation at http://capistranorb.com/#
way to automate apps and IT infrastructure ❖ Uses YAML syntax. ❖ Configuration details are organised in roles with each roles containing it’s own files, tasks, handlers, vars, templates. ❖ Playbooks contain roles and target hosts. ❖ Plenty of free tested roles available on https://galaxy.ansible.com ❖ Recently acquired by Redhat
❖ New Relic - Collect and display data on your apps, infrastructure. Real time updates. ❖ Cloud Watch - Monitoring as a service for AWS resources. Can monitor EC2 servers, RDS, DynamoDB... ❖ Nagios - Monitor your entire infrastructure - Systems, networks, infrastructure. nagios.org
Started in the Django community. Now a paid service. ❖ LogStash - Collect and analyze logs from various sources. ❖ Kibana - Collect, analyze, visualize, search your logs. ❖ Datadog - Collect and visualize various performance metrics from your apps.
❖ Git Flow Guidelines within the team ❖ Configuration Management & Orchestration with Ansible ❖ Daily, Weekly Builds ❖ Monitoring and Logging with Papertrail ❖ Issue Tracking and process of Solving bugs ❖ Think Agile
a build in one step? ❖ Do you make daily builds? ❖ Do you use configuration management tools to automate Infrastructure? ❖ Is the development documented and automated? ❖ Can you roll out and roll back deployments in one step? Credits @jmwai