dysinger

cat > Dockerfile <<\EOF
FROM ubuntu:12.04
RUN apt-get update
RUN apt-get install -y ruby1.9.3 build-essential \
    libc6-dev libffi-dev libgdbm-dev libncurses5-dev \
    libreadline-dev libssl-dev libyaml-dev zlib1g-dev
RUN gem install fpm --bindir=/usr/bin --no-rdoc --no-ri
RUN apt-get install -y curl
RUN curl ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.3-p484.tar.gz|tar oxzC /tmp
WORKDIR /tmp/ruby-1.9.3-p484

hkorte

curl -XDELETE 'http://localhost:9200/testindex?pretty=true'
curl -XPOST 'http://localhost:9200/testindex?pretty=true' -d '
{
   "mappings": {
      "testdoc": {
         "properties": {
            "name": {
               "type": "string"
            },
            "location": {

jzajpt

#!/usr/bin/env ruby
#
# haml2erb

require 'rubygems'
require 'haml'

class ErbEngine < Haml::Engine
  def push_script(text, preserve_script, in_tag = false, preserve_tag = false,
                  escape_html = false, nuke_inner_whitespace = false)

qrush

gemcutter => redis downloads spec
=================================

keys
----

downloads                     => global counter for all gem downloads
downloads:today               => sorted set for downloads from today
downloads:rubygem:rails       => counter for all rails downloads
downloads:version:rails-2.3.5 => counter for all rails 2.3.5 downloads

madhums

#config/initializers/omniauth.rb
require 'openid/store/filesystem'

ActionController::Dispatcher.middleware.use OmniAuth::Builder do #if you are using rails 2.3.x
#Rails.application.config.middleware.use OmniAuth::Builder do #comment out the above line and use this if you are using rails 3
  provider :twitter,  'key', 'secret'
  provider :facebook, 'app_id', 'secret'
  provider :linked_in, 'key', 'secret'
  provider :open_id,  OpenID::Store::Filesystem.new('/tmp')
end

porras

Why Steak (over Cucumber)

From here

• Plain text have no value if people writing and reading the specs are developers. Code is natural language for developers (specially if that code is Ruby). Having a client who reads the specs is a possible situation and Cucumber is cool there, but in my experience that situation is not the most common one. If in your case there's no value in having your specs in English rather than in Ruby, Cucumber is an additional layer of abstraction in exchange of nothing.

• There's a myth about clients writing the specs. It sounds like a unicorn to me, but let's take it. Still, I wouldn't want it. Clients are experts in problems, I am expert in solutions. I want the client to describe the problem I have to solve, not to describe the solution.

• Some people say Cucumber is cool because you write the stories, the client validates them, and then you can start developing. That is not Agile. The on

hron84

#!/usr/bin/ruby

require 'rubygems'
require 'haml'

class ErbEngine < Haml::Engine
  def push_script(text, opts = {} )
    push_text "<%= #{text.strip} %>"
  end
  

leshill

# Add this to more_web_steps.rb
# Selenium docs: http://code.google.com/p/selenium/wiki/RubyBindings#Javascript_Alert/Confirm today!

When /^I (accept|dismiss) the "([^"]*)" alert$/ do |action, text|
  alert = page.driver.browser.switch_to.alert
  alert.text.should eq(text)
  alert.send(action)
end

sstephenson

require File.dirname(__FILE__) + '/config/environment'
run ActionController::Dispatcher.new

ihower

Rails 3.1 overview

• https://gist.github.com/958283
• https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/milestones/71470-31
• http://hemju.com/2011/02/23/rails-3-1-release-rumors-and-news-about-features/
• http://www.hagenburger.net/TALKS/rails-3.1-frontend-performance.html#slide1

Railtie

Console shows SQL queries right there.