jagregory

So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear!

Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy.

* Off the top of my head *

1. Fork their repo on Github
2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it

    git remote add my-fork git@github...my-fork.git

3dd13

# gem "prawn", "0.8.4"
# Sometime there is no enough space for the last table row when it reaches the end of page

Prawn::Document.generate("text_group_overflow_question.pdf") do |pdf|
  add_page_break_if_overflow(pdf) do |pdf|
    # generating table here
    # ...
  end
end

mhenrixon

=semantic_form_for [:admin, @dog], validate: true, html: {multipart: true} do |f|
  =f.inputs do
    =f.input :name
    =f.input :kennel_name  
    =f.input :birthdate   
    =f.input :gender,    as: :radio,  collection: {'Tik' => 'F', 'Hane' => 'M'}
    =f.input :father_id, as: :select, collection: @dogs
    =f.input :mother_id, as: :select, collection: @bitches
    
    =f.semantic_fields_for :pictures do |pic|

rtwomey

Recently, I had a staging database on Heroku that was running on the Ronin database (which was originally the lowest-sized DB you could get at Heroku). Since they added two new options, Crane and Kappa, we wanted to take advantage of the cost savings. Here's how you can migrate your Ronin DB to Crane (or any other plan).

The old database was named BROWN while the new one is CRIMSON. You can determine this by running:

heroku pg:info --app myapp-staging

1. Add Crane database

    heroku addons:add heroku-postgresql:crane --app myapp-staging
   

heroku pg:wait --app myapp-staging

dblock

class DelayedJobObserver < Mongoid::Observer
  observe Delayed::Job

  class << self
    attr_accessor :total_processed
    attr_accessor :total_errors
    attr_accessor :enabled

    def enabled?
      !! DelayedJobObserver.enabled

ChromeOrange

<?php
/**
 * Standard Tab Code from woocommerce-hooks.php
 */
	/* Product page tabs */
	add_action( 'woocommerce_product_tabs', 'woocommerce_product_description_tab', 10 );
	add_action( 'woocommerce_product_tabs', 'woocommerce_product_attributes_tab', 20 );
	add_action( 'woocommerce_product_tabs', 'woocommerce_product_reviews_tab', 30 );

	add_action( 'woocommerce_product_tab_panels', 'woocommerce_product_description_panel', 10 );

rjz

# A class-based template for jQuery plugins in Coffeescript
#
#     $('.target').myPlugin({ paramA: 'not-foo' });
#     $('.target').myPlugin('myMethod', 'Hello, world');
#
# Check out Alan Hogan's original jQuery plugin template:
# https://github.com/alanhogan/Coffeescript-jQuery-Plugin-Template
#
(($, window) ->

sunny

# encoding: UTF-8
#
#     $ rake checkout new_branch_name
#
# Via https://gist.github.com/jonlemmon/4076864
#
# 1. Roll back any migrations on your current branch which do not exist on the
#    other branch
# 2. Discard any changes to the db/schema.rb file
# 3. Check out the other branch

speric

Chapter 1 - Object Oriented Design

The purpose of design is to allow you to do design later, and it's primary goal is to reduce the cost of change.

SOLID Design:

• Single Responsibility Principle: a class should have only a single responsibility
• Open-Closed Principle: Software entities should be open for extension, but closed for modification (inherit instead of modifying existing classes).
• Liskov Substitution: Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program.
• Interface Segregation: Many client-specific interfaces are better than one general-purpose interface.

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