weppos

# 
# = Capistrano database.yml task
#
# Provides a couple of tasks for creating the database.yml 
# configuration file dynamically when deploy:setup is run.
#
# Category::    Capistrano
# Package::     Database
# Author::      Simone Carletti <[email protected]>
# Copyright::   2007-2010 The Authors

trevorturk

We couldn’t find that file to show.

mislav

connection = Faraday::Connection.new('http://example.com') do |builder|
  builder.request :url_encoded  # for POST/PUT params
  builder.adapter :net_http
end

# same as above, short form:
connection = Faraday.new 'http://example.com'

# GET
connection.get '/posts'

paulsturgess

Your Class:

class YourClass < ActiveRecord::Base
  attr_accessor :some_date
  columns_hash["some_date"] = ActiveRecord::ConnectionAdapters::Column.new("some_date", nil, "date")
end

Your View:

<%= form_for :your_class do |f| %>

traviskaufman

Better Jasmine Tests With this

On the Refinery29 Mobile Web Team, codenamed "Bicycle", all of our unit tests are written using Jasmine, an awesome BDD library written by Pivotal Labs. We recently switched how we set up data for tests from declaring and assigning to closures, to assigning properties to each test case's this object, and we've seen some awesome benefits from doing such.

The old way

Up until recently, a typical unit test for us looked something like this:

describe('views.Card', function() {