dfl

# mysql db backup and restore for rails
# by David Lowenfels <david@internautdesign.com>  4/2011

require 'yaml'

namespace :db do
  def backup_prep
    @directory = File.join(RAILS_ROOT, 'db', 'backup')
    @db = YAML::load( File.open( File.join(RAILS_ROOT, 'config', 'database.yml') ) )[ RAILS_ENV ]
    @db_params = "-u #{@db['username']} #{@db['database']}"

rgabo

Reasons why we did not go with Elastic Beanstalk

tldr;

Elastic Beanstalk with Docker is great at having a standard way of running and scaling out web and worker applications, if you are OK with AWS abstractions and further lock-in. For instance, auto-scaling web apps using autoscaling group policies is extremely powerful, but I believe there is a lot of accidental complexity that comes with Elastic Beanstalk so we chose something that we believe is simpler and easier to understand or change.

not so tldr;

1. AWS is great at taking an existing technology, wrapping it into AWS-specific concepts and creating a proprietary JSON/XML API around it. This is why ECS Task Definitions exist. Elastic Beanstalk goes one step further and creates yet another layer of API on top of ECS and ELB aptly called Dockerrun.aws.json v2. The format is proprietary and we preferred ex

tmichel

Shell cheat sheet

Setting up iTerm

• Use option as meta key:

Go to Preferences->Profiles tab. Select your profile on the left, and then open the Keyboard tab. At the bottom is a set of buttons that lets you select the behavior of the Option key. For most users, Esc+ will be the best choice.

• Setting up word-by-word movement with Option+: