Anthony Aerlinger

A Capistrano Rails Guide

by Jonathan Rochkind, http://bibwild.wordpress.com

why cap?

Capistrano automates pushing out a new version of your application to a deployment location.

I've been writing and deploying Rails apps for a while, but I avoided using Capistrano until recently. I've got a pretty simple one-host deployment, and even though everyone said Capistrano was great, every time I tried to get started I just got snowed under not being able to figure out exactly what I wanted to do, and figured I wasn't having that much trouble doing it "manually".

OpsWorks

AWS OpsWorks, formerly Scalarium, is a chef-based system that deeply integrates with EC2 (security policies, key pairs, etc). OpsWorks acts as web console to configure your entire system, and as a command hub for running chef-solo on all the instances.

Stacks

A stack represents a collection of inter-connected and inter-configured services.

A stack has lifecycle events which are triggered by any change to the stack configuration (such as, adding a new instance to a layer, or changing the hosts of an application). In this way, the stack acts as an event hub, notifying every instance of any changes.

belongs_to:

Assigning an object to a belongs_to association does not automatically save the object. It does not save the associated object either.

has_one:

When you assign an object to a has_one association, that object is automatically saved (in order to update its foreign key).
In addition, any object being replaced is also automatically saved, because its foreign key will change too
If either of these saves fails due to validation errors, then the assignment statement returns false and the assignment itself is cancelled.
If the parent object (the one declaring the has_one association) is unsaved (that is, new_record? returns true) then the child objects are not saved. They will automatically when the parent object is saved.

belongs_to:

Assigning an object to a belongs_to association does not automatically save the object. It does not save the associated object either.

has_one:

When you assign an object to a has_one association, that object is automatically saved (in order to update its foreign key).
In addition, any object being replaced is also automatically saved, because its foreign key will change too
If either of these saves fails due to validation errors, then the assignment statement returns false and the assignment itself is cancelled.
If the parent object (the one declaring the has_one association) is unsaved (that is, new_record? returns true) then the child objects are not saved. They will automatically when the parent object is saved.

Big List of Real Estate APIs

Listings / Property Data

####Rets Rabbit http://www.retsrabbit.com

Rets Rabbit removes the nightmare of importing thousands of real estate listings and photos from RETS or ListHub and gives you an easy to use import and Web API server so you can focus on building your listing search powered website or app.

	$(function(){
	railsMonthDates();
	$("select[id=_2i], select[id=_1i]").change( railsMonthDates );
	});

	function railsMonthDates() {
	$("select[id*=_2i]").each(function(){
	$monthSelect = $(this);
	$daySelect = $(this).siblings("select[id*=_3i]");
	$yearSelect = $(this).siblings("select[id*=_1i]");

	<!DOCTYPE html>
	<html>
	<head>
	<meta charset="utf-8">
	<title></title>
	<link rel="stylesheet" href="../libs/mocha.css" type="text/css" media="screen" title="no title" charset="utf-8">
	</head>
	<body>
	<div id="mocha"></div>
	<script src="../libs/mocha.js" type="text/javascript" charset="utf-8"></script>

	<%= simple_form_for @product do \|f\| %>
	<%= f.simple_fields_for :attributes do \|d\| %>

	<% f.object.attributes.try(:each) do \|key, value\| %>
	<%= d.input key, :input_html => {:value => value } %>
	<% end %>

	<% end %>
	<% end %>