Logan Hasson loganhasson

Multiple SSH Keys settings for different github account

create different public key

create different ssh key according the article Mac Set-Up Git

$ ssh-keygen -t rsa -C "your_email@youremail.com"

tmux cheat sheet

(C-x means ctrl+x, M-x means alt+x)

Prefix key

The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:

remap prefix to Control + a

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

S3 Website "Index Document"

`index.html`:

<html>
<head>
<title>403 Forbidden</title>
</head>
<body>

My issues with Modules

In researching topics for RailsCasts I often read code in Rails and other gems. This is a great exercise to do. Not only will you pick up some coding tips, but it can help you better understand what makes code readable.

A common practice to organize code in gems is to divide it into modules. When this is done extensively I find it becomes very difficult to read. Before I explain further, a quick detour on instance_eval.

You can find instance_eval used in many DSLs: from routes to state machines. Here's an example from Thinking Sphinx.

class Article &lt; ActiveRecord::Base

	=Navigating=
	visit('/projects')
	visit(post_comments_path(post))

	=Clicking links and buttons=
	click_link('id-of-link')
	click_link('Link Text')
	click_button('Save')
	click('Link Text') # Click either a link or a button
	click('Button Value')

	after "deploy:symlink", "deploy:restart_workers"

	##
	# Rake helper task.
	# http://pastie.org/255489
	# http://geminstallthat.wordpress.com/2008/01/27/rake-tasks-through-capistrano/
	# http://ananelson.com/said/on/2007/12/30/remote-rake-tasks-with-capistrano/
	def run_remote_rake(rake_cmd)
	rake_args = ENV['RAKE_ARGS'].to_s.split(',')
	cmd = "cd #{fetch(:latest_release)} && #{fetch(:rake, "rake")} RAILS_ENV=#{fetch(:rails_env, "production")} #{rake_cmd}"

	body {
	font-family: Helvetica, arial, sans-serif;
	font-size: 14px;
	line-height: 1.6;
	padding-top: 10px;
	padding-bottom: 10px;
	background-color: white;
	padding: 30px; }

	body > *:first-child {

	# When an RSpec test like this fails,
	#
	# @my_array.should == [@some_model, @some_model2]
	#
	# RSpec will call inspect on each of the objects to "help" you figure out
	# what went wrong. Well, inspect will usually dump a TON OF SHIT and make trying
	# to figure out why `@my_array` is not made up of `@some_model` and `@some_model2`.
	#
	# This little module and technique helps get around that. It will redefine `inspect`
	# if you include it in your model object.

	# lib/tasks/deploy.rake
	namespace :deploy do
	desc 'Deploy to staging environment'
	task :staging do
	exec 'mina deploy -f config/deploy/staging.rb'
	end
	end