lucashungaro

To install mkvtoolnix:

$ brew install mkvtoolnix


To split a file:

$ mkvmerge --split size:4050m /path/to/file.mkv -o /path/to/output_file.mkv

lucashungaro

# Add all gems in the global gemset to the $LOAD_PATH so they can be used in rails3 console with bundler
if defined?(::Bundler)
  $LOAD_PATH.concat Dir.glob("#{ENV['rvm_ruby_global_gems_path']}/gems/*/lib")
end

lucashungaro

describe Post do
  context "data validation" do
    subject { Factory.build(:post) }

    it "requires a title" do
      subject.title = nil
      subject.should_not be_valid
    end

    it "requires a body" do

lucashungaro

# on config/boot.rb

require "yaml"
YAML::ENGINE.yamler= "syck"

lucashungaro

# Add all gems installed in the system to the $LOAD_PATH so they can be used in Rails console with Bundler
if defined?(::Bundler)
  current_ruby_version = `rbenv version`.split(" ").first
  gem_paths = Dir.glob("#{ENV["HOME"]}/.rbenv/versions/#{current_ruby_version}/lib/ruby/gems/**/gems/*/lib")
  gem_paths.each do |path|
    $LOAD_PATH << path
  end
end

# now you can just normally install these gems ('gem install <gem-name>') into your system and keep your Gemfile listing only your app's dependencies. I use this with wirble, awesome_print and looksee and it works just fine. :)

lucashungaro

class Lists < App
  all { List.all } # :get /lists
  one { List.find(params[:id]) } # :get /lists/:id
  instance { List.new(params[:list]) }

  to_update { list.update_attributes(params[:list]) }
  to_destroy { list.destroy }

  # If you want to set an action for this resource only.
  get :search do

lucashungaro

class Lists < App
  authenticate { AuthenticationService.authenticate(session) } # just an example, it checks for true or false only
  authorize { current_user.role? :admin }, :for => :create, :update # same here
  
  all { List.all } # :get /lists

  # the param name should always be class.name.singularize
  one { List.find(params[:list]) } # :get /lists/:id
  instance { List.new(params[:list]) }

lucashungaro

"Why You Don't Get Mock Objects" by Gregory Moeck

RubyConf 2011 | 2011-09-29 | Gregory Moeck (@gregmoeck) | Slides

• Recommended as the best book on mocks: Growing Object-Oriented Software, Guided by Tests by Steve Freeman & Nat Pryce
• Common arguments against mocks
  • They duplicate implementation
  • They lead to brittle tests
• Mock objects + procedural programming = bad idea
• If you're doing traditional Rails development (which tends to follow more of a "procedural", do-this-and-then-do-that style), mock objects probably aren't for you

lucashungaro

class Game < ActiveRecord::Base
  belongs_to :category
  validates_presence_of :title, :category_id, :description,
                        :price, :platform, :year

  def get_official_price
    open("http://thegamedatabase.com/api/game/#{name}/price?api_key=ek2o1je")
  end

  def print

lucashungaro

class Game < ActiveRecord::Base
  belongs_to :category
  validates_presence_of :title, :category_id, :description,
                        :price, :platform, :year
end

class GamePriceService
  attr_accessor :game

  # we could use a config file