| You are trying to install in deployment mode after changing | |
| your Gemfile. Run `bundle install` elsewhere and add the | |
| updated Gemfile.lock to version control. | |
| You have deleted from the Gemfile: | |
| * guard-pow | |
| * rb-fsevent |
| class Settings < Settingslogic | |
| source "#{Rails.root}/config/application.yml" | |
| if Rails.env == 'development' | |
| namespace 'development-' + Socket.gethostname.gsub(/\W/, '-').gsub(/[-]{2,}/, '-') | |
| else | |
| namespace Rails.env | |
| end | |
| # load local settings |
cribbed from http://pastebin.com/xgzeAmBn
Templates to remind you of the options and formatting for the different types of objects you might want to document using YARD.
As configured in my dotfiles.
start new:
tmux
start new with session name:
| class ActionDispatch::Routing::Mapper | |
| def draw(routes_name) | |
| instance_eval(File.read(Rails.root.join("config/routes/#{routes_name}.rb"))) | |
| end | |
| end | |
| BCX::Application.routes.draw do | |
| draw :api | |
| draw :account | |
| draw :session |
Originally published in June 2008
When hiring Ruby on Rails programmers, knowing the right questions to ask during an interview was a real challenge for me at first. In 30 minutes or less, it's difficult to get a solid read on a candidate's skill set without looking at code they've previously written. And in the corporate/enterprise world, I often don't have access to their previous work.
To ensure we hired competent ruby developers at my last job, I created a list of 15 ruby questions -- a ruby measuring stick if you will -- to select the cream of the crop that walked through our doors.
Candidates will typically give you a range of responses based on their experience and personality. So it's up to you to decide the correctness of their answer.
| # This is a skeleton for testing models including examples of validations, callbacks, | |
| # scopes, instance & class methods, associations, and more. | |
| # Pick and choose what you want, as all models don't NEED to be tested at this depth. | |
| # | |
| # I'm always eager to hear new tips & suggestions as I'm still new to testing, | |
| # so if you have any, please share! | |
| # | |
| # @kyletcarlson | |
| # | |
| # This skeleton also assumes you're using the following gems: |
| # This custom matcher can be used to test state machine | |
| # | |
| # Examples | |
| # | |
| # it { should have_event(:status, :event_name, [:state1, :state2] => [:state3, :state4]) } | |
| # it { should have_event(:status, :event_name, { | |
| # :state1 => :state3, | |
| # :state1 => :state4, | |
| # :state3 => :state3, | |
| # :state2 => :state4 |
http://ruby-china.org/topics/16256
get https://github.com/mvj3/hangman/blob/master/data/words.txt
and compile the decision tree.json
ruby compile.rb| class Ticket < ActiveRecord::Base | |
| belongs_to :grouper | |
| belongs_to :user | |
| validate :user_cant_be_blacklisted, on: :confirmation | |
| validate :user_cant_double_book, on: :confirmation | |
| validate :grouper_cant_be_full, on: :confirmation | |
| validate :grouper_cant_have_occurred, on: :confirmation |