mnutt

Instrument Anything in Rails 3

With Rails 3.0 released a few weeks ago I've migrated a few apps and I'm constantly finding useful new improvements. One such improvement is the ability to log anything in the same way that Rails internally logs ActiveRecord and ActionView. By default Rails 3 logs look slightly spiffier than those produced by Rails 2.3: (notice the second line has been cleaned up)

Started GET "/" for 127.0.0.1 at Mon Sep 06 01:07:11 -0400 2010
  Processing by HomeController#index as HTML
  User Load (0.2ms)  SELECT `users`.* FROM `users` WHERE (`users`.`id` = 3) LIMIT 1
  CACHE (0.0ms)  SELECT `users`.* FROM `users` WHERE (`users`.`id` = 3) LIMIT 1

Rendered layouts/_nav.html.erb (363.4ms)

sr

source "http://rubygems.org"
gem "janky", "~>0.9"
gem "pg"
gem "thin"

dhh

class PostsController < ActionController::Base
  def create
    Post.create(post_params)
  end
  
  def update
    Post.find(params[:id]).update_attributes!(post_params)
  end

  private

MohamedAlaa

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

toddwschneider

# you can make a text file of request times (in ms, one number per line) and import it here, or you can use a probability distribution to simulate request times (see below where setting req_durations_in_ms)
# rq = read.table("~/Downloads/request_times.txt", header=FALSE)$V1

# argument notes:
# parallel_router_count is only relevant if router_mode is set to "intelligent"
# choice_of_two, power_of_two, and unicorn_workers_per_dyno are only relevant if router_mode is set to "naive"
# you can only select one of choice_of_two, power_of_two, and unicorn_workers_per_dyno

run_simulation = function(router_mode = "naive",
                          reqs_per_minute = 9000,

leshill

require 'spec_helper'

describe 'Jasmine suite', :js do
  def run_jasmine_tests
    visit '/jasmine'
    Timeout.timeout(10) do
      while page.has_css?('.runningAlert')
        sleep 0.25
      end
    end

adamwiggins

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style

atmos

$ rails new foo
      create  
      create  README.rdoc
...
~$ cd foo
~/foo$ git init
Initialized empty Git repository in /Users/atmos/foo/.git/
~/foo$ git add .
~/foo$ git commit -m "initial import"
[master (root-commit) c3392c9] initial import

drush

# Only run in server process, not console or rake tasks
if !Rails.const_defined?('Console') && !($0 =~ /rake$/) && !Rails.env.test?
  Rails.application.config.after_initialize do

    (1..2).each do |thread_id| 
      Thread.new { 
        Thread.current[:thread_name] = "DJ Web Worker Thread #{thread_id}"
        ActiveRecord::Base.connection_pool.with_connection do |conn|
          dj = Delayed::Worker.new
          Rails.logger.warn "Starting #{Thread.current[:thread_name]}"

seapy

RailsConf 2015 Schedule

RailsConf 2015 Room 202 Day 1

• Opening Keynote - DHH
• Prying Open The Black Box - Godfrey Chan
  • slide
• Riding Rails for 10 Years - John Duff
• DevOps for The Lazy - Aja Hammerly
• Docker isn’t just for deployment - Ben Dixon