szalansky

## people_controller.rb

class PeopleController < ApplicationController
  before_filter :authenticate_user!, :except => [:index, :show]
...
end

## clojure.md

      
              1 file
            
          
              21 forks
            
          
              8 comments
            
          
              130 stars
            
          
                rakhmad
                / clojure.md
            
            
              Created
              April 17, 2012 15:55
            
              
                Setting Up Clojure on OS X
              
          
    Setting Up Clojure on OS X

I spent a lot of time trying to find a pretty optimal (for me) setup for Clojure… at the same time I was trying to dive in and learn it. This is never optimal; you shouldn't be fighting the environment while trying to learn something.
I feel like I went through a lot of pain searching Google, StackOverflow, blogs, and other sites for random tidbits of information and instructions.
This is a comprehensive "what I learned and what I ended up doing" that will hopefully be of use to others and act as a journal for myself if I ever have to do it again. I want to be very step-by-step and explain what's happening (and why) at each step.
Step 1: Getting Clojure (1.3)


## extend.rb
module A
  extend SelfishModule
  def abc; end
end

module B
  extend SelfishModule
  def bcd; end
end

## raskell.rb
$stack, $draws = [], {}

def method_missing *args
  return if args[0][/^to_/]
  $stack << args.map { |a| a or $stack.pop }
  $draws[$stack.pop(2)[0][0]] = args[1] if args[0] == :<
end

class Array
  def +@

## hash.rb
# Instead of:
#    hash[:a].try(:[], :b).try(:[], :c).try(:[], :d)
# you can write
#    hash[:a, :b, :c, :d]

class Hash
  # h = {:a => {:b => {:c => 1}}}
  # p h[:a]             # => {:b => {:c => 1}}
  # p h[:a, :b]         # => {:c => 1}
  # p h[:a, :b, :c]     # => 1

## web_steps.rb
# TL;DR: YOU SHOULD DELETE THIS FILE
#
# This file was generated by Cucumber-Rails and is only here to get you a head start
# These step definitions are thin wrappers around the Capybara/Webrat API that lets you
# visit pages, interact with widgets and make assertions about page content.
#
# If you use these step definitions as basis for your features you will quickly end up
# with features that are:
#
# * Hard to maintain

## list_comprehension.rb
#!/usr/bin/env ruby-head

class VeryBasicObject < BasicObject
  undef :==
  undef :!=
  undef :!
end

class Captured < VeryBasicObject
  def method_missing meth, *args

## rubocop_pre_commit_hook
#!/usr/bin/env ruby

require 'english'
require 'rubocop'

ADDED_OR_MODIFIED = /A|AM|^M/.freeze

changed_files = `git status --porcelain`.split(/\n/).
    select { |file_name_with_status|
      file_name_with_status =~ ADDED_OR_MODIFIED

## attr_capcessor.rb
module Cappy
  def attr_capcessor attr
    attr_reader attr.to_sym

    define_method "#{attr}=" do |value|
      instance_variable_set("@#{attr}", value.to_s.upcase)
    end
  end
end

## gist:9742059
App configuration in environment variables: for and against

For (some of these as per the 12 factor principles)

1) they are are easy to change between deploys without changing any code

2) unlike config files, there is little chance of them being checked
into the code repo accidentally

3) unlike custom config files, or other config mechanisms such as Java

	class PeopleController < ApplicationController
	before_filter :authenticate_user!, :except => [:index, :show]
	...
	end
	module A
	extend SelfishModule
	def abc; end
	end

	module B
	extend SelfishModule
	def bcd; end
	end
	$stack, $draws = [], {}

	def method_missing *args
	return if args[0][/^to_/]
	$stack << args.map { \|a\| a or $stack.pop }
	$draws[$stack.pop(2)[0][0]] = args[1] if args[0] == :<
	end

	class Array
	def +@
	# Instead of:
	# hash[:a].try(:[], :b).try(:[], :c).try(:[], :d)
	# you can write
	# hash[:a, :b, :c, :d]

	class Hash
	# h = {:a => {:b => {:c => 1}}}
	# p h[:a] # => {:b => {:c => 1}}
	# p h[:a, :b] # => {:c => 1}
	# p h[:a, :b, :c] # => 1
	# TL;DR: YOU SHOULD DELETE THIS FILE
	#
	# This file was generated by Cucumber-Rails and is only here to get you a head start
	# These step definitions are thin wrappers around the Capybara/Webrat API that lets you
	# visit pages, interact with widgets and make assertions about page content.
	#
	# If you use these step definitions as basis for your features you will quickly end up
	# with features that are:
	#
	# * Hard to maintain
	#!/usr/bin/env ruby-head

	class VeryBasicObject < BasicObject
	undef :==
	undef :!=
	undef :!
	end

	class Captured < VeryBasicObject
	def method_missing meth, *args
	#!/usr/bin/env ruby

	require 'english'
	require 'rubocop'

	ADDED_OR_MODIFIED = /A\|AM\|^M/.freeze

	changed_files = `git status --porcelain`.split(/\n/).
	select { \|file_name_with_status\|
	file_name_with_status =~ ADDED_OR_MODIFIED
	module Cappy
	def attr_capcessor attr
	attr_reader attr.to_sym

	define_method "#{attr}=" do \|value\|
	instance_variable_set("@#{attr}", value.to_s.upcase)
	end
	end
	end
	App configuration in environment variables: for and against

	For (some of these as per the 12 factor principles)

	1) they are are easy to change between deploys without changing any code

	2) unlike config files, there is little chance of them being checked
	into the code repo accidentally

	3) unlike custom config files, or other config mechanisms such as Java