tansengming

# Copy and paste this to the rails console to test your email settings

class MyMailer < ActionMailer::Base
  def test_email
    @recipients = "someone@somewhere.com"
    @from = "must_be_same_as_smpt_account_login@gmail.com"
    @subject = "test from the Rails Console"
    @body = "This is a test email"
  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|

Sujimichi

class ApplicationController < ActionController::Base

  ...
  #Problem:
  #In rails 3.0.1+ it is no longer possible to do this anymore;
  #  rescue_from ActionController::RoutingError, :with => :render_not_found
  #
  #The ActionController::RoutingError thrown is not caught by rescue_from.
  #The alternative is to to set a catch-all route to catch all unmatched routes and send them to a method which renders an error
  #As in http://techoctave.com/c7/posts/36-rails-3-0-rescue-from-routing-error-solution

vsavkin

Building Rich Domain Models in Rails.

Part 1. Decoupling Persistence.

Abstract

Domain model is an effective tool for software development. It can be used to express really complex business logic, and to verify and validate the understanding of the domain among stakeholders. Building rich domain models in Rails is hard. Primarily, because of Active Record, which doesn't play well with the domain model approach.

One way to deal with this problem is to use an ORM implementing the data mapper pattern. Unfortunately, there is no production ready ORM doing that for Ruby. DataMapper 2 is going to be the first one.

Another way is to use Active Record just as a persistence mechanism and build a rich domain model on top of it. That's what I'm going to talk about in this article.

Fitzsimmons

Building Rich Domain Models in Rails

Part 1. Decoupling Persistence

Abstract

Domain model is an effective tool for software development. It can be used to express really complex business logic, and to verify and validate the understanding of the domain among stakeholders. Building rich domain models in Rails is hard. Primarily, because of Active Record, which doesn't play well with the domain model approach.

One way to deal with this problem is to use an ORM implementing the data mapper pattern. Unfortunately, there is no production ready ORM doing that for Ruby. DataMapper 2 is going to be the first one.

Another way is to use Active Record just as a persistence mechanism and build a rich domain model on top of it. That's what I'm going to talk about here.

jgv

FactoryGirl.define do
  factory :picture do
    image { File.open(File.join(Rails.root, 'spec', 'support', 'pictures', 'spec.png')) }
  end
end

vsavkin

#somewhere in a controller

CreateOrder.new(OrderRepository).create current_user, params


# where

class CreateOrder < UseCaseService
  def initialize order_repo
    @order_repo = order_repo    

SabretWoW

# 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: 

jtadeulopes

Update and upgrade the system

sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade && sudo apt-get autoremove
sudo reboot

Configure timezone

blackfalcon

Git-workflow vs feature branching

When working with Git, there are two prevailing workflows are Git workflow and feature branches. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited, and the focus of this article.

If you are new to Git and Git-workflows, I suggest reading the atlassian.com Git Workflow article in addition to this as there is more detail there than presented here.

I admit, using Bash in the command line with the standard configuration leaves a bit to be desired when it comes to awareness of state. A tool that I suggest using follows these instructions on setting up GIT Bash autocompletion. This tool will assist you to better visualize the state of a branc