hectoregm

How to Ruby Debug with Pow

Below are steps I followed to get ruby debugger ruby-debug running with Pow. Based on info from this thread basecamp/pow#43 and this blog post http://flochip.com/2011/04/13/running-pow-with-rdebug/

1) Update your Gemfile

Assuming you're writing your app in Ruby 1.9 and using Bundler, just add the dependency to your development gems:

hectoregm

MyView = Backbone.View.extend({

  events: {
    "click #someButton": "doThat",
    "change #someInput": "changeIt"
  },

  doThat: function(){ ... },
  changeIt: function(){ ... }
});

hectoregm

- http://www.coffeepowered.net/2009/06/13/fine-tuning-your-garbage-collector/
- http://snaprails.tumblr.com/post/241746095/rubys-gc-configuration

  article’s settings:                                     ("spec spec" took 17-23!sec)
	export RUBY_HEAP_MIN_SLOTS=1250000
	export RUBY_HEAP_SLOTS_INCREMENT=100000
	export RUBY_HEAP_SLOTS_GROWTH_FACTOR=1
	export RUBY_GC_MALLOC_LIMIT=30000000
	export RUBY_HEAP_FREE_MIN=12500

hectoregm

user  nginx;
worker_processes  5;

error_log  /var/log/nginx.error.log;
pid        /var/run/nginx.pid;

events {
  worker_connections  1024;
}

hectoregm

- http://www.coffeepowered.net/2009/06/13/fine-tuning-your-garbage-collector/
- http://snaprails.tumblr.com/post/241746095/rubys-gc-configuration

  article’s settings:                                     ("spec spec" took 17-23!sec)
	export RUBY_HEAP_MIN_SLOTS=1250000
	export RUBY_HEAP_SLOTS_INCREMENT=100000
	export RUBY_HEAP_SLOTS_GROWTH_FACTOR=1
	export RUBY_GC_MALLOC_LIMIT=30000000
	export RUBY_HEAP_FREE_MIN=12500

hectoregm

Client-side SSL

For excessively paranoid client authentication.

Using self-signed certificate.

Create a Certificate Authority root (which represents this server)

Organization & Common Name: Some human identifier for this server CA.

openssl genrsa -des3 -out ca.key 4096
openssl req -new -x509 -days 365 -key ca.key -out ca.crt

hectoregm

gem 'pg'
group :development do
	gem 'ruby-debug'
end
gem 'rake', '~> 0.8.7'
gem 'devise'
gem 'oa-oauth', :require => 'omniauth/oauth'
gem 'omniauth'
gem 'haml'
gem 'dynamic_form'

hectoregm

Steps

• Build tools:

    sudo yum groupinstall "Development Tools"
  

• Dependencies:

    yum install -y gcc-c++ patch readline readline-devel zlib zlib-devel \
  

libyaml-devel libffi-devel openssl-devel make bzip2 autoconf automake libtool bison iconv-devel

hectoregm

Jim Weirich:

This is how I explain it… Ruby has Procs and Lambdas. Procs are created with Proc.new { }, lambdas are created with lambda {} and ->() {}.

In Ruby 1.8, proc {} creates lambda, and Ruby 1.9 it creates procs (don't ask).

Lambdas use method semantics when handling parameters, procs use assignment semantics when handling parameters.

This means lambdas, like methods, will raise an ArgumentError when called with fewer arguments than they were defined with. Procs will simply assign nil to variables for arguments that were not passed in.

hectoregm

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying