| [ -f $HOME/.profile ] && . $HOME/.profile | |
| HISTSIZE=2000 | |
| SAVEHIST=$HISTSIZE | |
| HISTFILE=$HOME/.zsh_history | |
| setopt append_history | |
| setopt inc_append_history | |
| setopt extended_history | |
| setopt hist_find_no_dups | |
| setopt hist_ignore_all_dups |
This Gist shows how to set up a Rails project to practice BDD with CoffeeScript, Guard and Jasmine. You can see this setup in action on Vimeo
bundle installmate Guardfilebundle exec jasmine initmate spec/support/yasmine.ymbundle exec guard
| <?xml version="1.0" encoding="UTF-8"?> | |
| <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> | |
| <plist version="1.0"> | |
| <dict> | |
| <key>fileTypes</key> | |
| <array> | |
| <string>feature</string> | |
| </array> | |
| <key>firstLineMatch</key> | |
| <string>기능|機能|功能|フィーチャ|خاصية|תכונה|Функціонал|Функционалност|Функционал|Особина|Могућност|Özellik|Właściwość|Tính năng|Savybė|Požiadavka|Požadavek|Osobina|Ominaisuus|Omadus|OH HAI|Mogućnost|Mogucnost|Jellemző|Fīča|Funzionalità|Funktionalität|Funkcionalnost|Funkcionalitāte|Funcționalitate|Functionaliteit|Functionalitate|Funcionalitat|Funcionalidade|Fonctionnalité|Fitur|Feature|Egenskap|Egenskab|Crikey|Característica|Arwedd(.*)</string> |
| require 'chunky_png' | |
| module ChunkyPNG::Color | |
| def h(value) | |
| r,g,b = r(value).to_f / MAX, g(value).to_f / MAX, b(value).to_f / MAX | |
| min, max = [r,g,b].minmax | |
| return 0 if max == min |
| gem "minitest" | |
| require "minitest/spec" | |
| require "minitest/autorun" | |
| require "active_model" | |
| require "turn" | |
| require "shoulda-matchers" | |
| class MiniTest::Unit::TestCase | |
| include Shoulda::Matchers::ActiveModel | |
| extend Shoulda::Matchers::ActiveModel |
by Jonathan Rochkind, http://bibwild.wordpress.com
Capistrano automates pushing out a new version of your application to a deployment location.
I've been writing and deploying Rails apps for a while, but I avoided using Capistrano until recently. I've got a pretty simple one-host deployment, and even though everyone said Capistrano was great, every time I tried to get started I just got snowed under not being able to figure out exactly what I wanted to do, and figured I wasn't having that much trouble doing it "manually".
| # First, make sure that you have the most recent rvm. Several bugs with 2.0.0-preview1 | |
| # have recently been fixed. | |
| # | |
| # Second, the openssl that comes with MacOS is too old for Ruby 2.0. You need to install | |
| # a newer one with homebrew or the rvm pkg command. | |
| # Option 1, with homebrew openssl: | |
| brew update | |
| brew install openssl |
| Capybara.add_selector :record do | |
| xpath { |record| XPath.css("#" + ActionController::RecordIdentifier.dom_id(record)) } | |
| match { |record| record.is_a?(ActiveRecord::Base) } | |
| end |
| #!/usr/bin/env ruby | |
| # | |
| # Usage: | |
| # irbify.rb script.rb | heroku run rails console --app=my-app | |
| # | |
| # Why eval and not piping directly? Piping directly would run all lines even if previous line was an invalid statement. | |
| # | |
| script_name = ARGV[0] |
My largest Sidekiq application had a memory leak and I was able to find and fix it in just few hours spent on analyzing Ruby's heap. In this post I'll show my profiling setup.
As you might know Ruby 2.1 introduced a few great changes to ObjectSpace, so now it's much easier to find a line of code that is allocating too many objects. Here is great post explaining how it's working.
I was too lazy to set up some seeding and run it locally, so I checked that test suite passes when profiling is enabled and pushed debugging to production. Production environment also suited me better since my jobs data can't be fully random generated.
So, in order to profile your worker, add this to your Sidekiq configuration:
if ENV["PROFILE"]