Aleksandar Popovic alekpopovic

Background

I believe Ubuntu 16.04 comes with PostgreSQL 9.5. Thats good for a start, but it is a matter of time before you have the need of a PostgreSQL 9.6 cluster. For me it was to import a PG backup from Heroku.

The procedure couldn't have been any easier and is described below. If you are interested in upgrading your old cluster to 9.6 afterwards, you may be interested in this.

Instructions

This is an example of how I combine interaction/service classes with Wisper event broadcasting in Rails.

In this example, I show a UsersController#create API, a corresponding service object, and all the test code/listeners to make it all happen.

The outcome is:

Concepts in your system ("Signing up a user", "Creating an order") have a single entry point in your codebase, vs. making raw ActiveRecord calls to object.save in dozens of places.
Since your concept has one entry point (the service class), you can easily grep for usage of it.
Stupid easy to attach listeners to the service class
All event listeners are very small and easily unit tested

How to reset PG Database on Heroku?

Step 1: heroku restart
Step 2: heroku pg:reset DATABASE (no need to change the DATABASE)
Step 3: heroku run rake db:migrate
Step 4: heroku run rake db:seed (if you have seed)

One liner

heroku restart; heroku pg:reset DATABASE --confirm APP-NAME; heroku run rake db:migrate

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

	HTTP status code symbols for Rails

	Thanks to Cody Fauser for this list of HTTP responce codes and their Ruby on Rails symbol mappings.

	Status Code Symbol
	1xx Informational
	100 :continue
	101 :switching_protocols
	102 :processing

	#!/usr/bin/env bash

	sudo locale-gen en_US.UTF-8
	sudo update-locale LANG=en_US.UTF-8
	sudo update-locale LC_ALL=en_US.UTF-8

	sudo apt-get update
	sudo apt-get install -y build-essential git curl libxslt1-dev libxml2-dev libssl-dev

	# postgres

	class Api::RegistrationsController < Api::BaseController

	respond_to :json
	def create

	user = User.new(params[:user])
	if user.save
	render :json=> user.as_json(:auth_token=>user.authentication_token, :email=>user.email), :status=>201
	return
	else

	Regex to match parts of a domain
	http://stackoverflow.com/questions/4636497/regular-expression-match-domain-in-uri

	^[^\/]+:\/\/[^\/]*?\.?([^\/.]+)\.[^\/.]+(?::\d+)?\/
	http://www.rubular.com/r/Uv5ON7eAz4

	^ # Match the beginning of the string
	[^\/]+:\/\/ # Match the protocol (e.g. http://)
	[^\/]*? # Non-greedy match of the sub-domains
	\.? # Optional . (for when a sub-domain is used)

	#
	# Wide-open CORS config for nginx
	#
	location / {

	if ($request_method = 'OPTIONS') {

	add_header 'Access-Control-Allow-Origin' '*';

	#

	#
	# CORS header support
	#
	# One way to use this is by placing it into a file called "cors_support"
	# under your Nginx configuration directory and placing the following
	# statement inside your location block(s):
	#
	# include cors_support;
	#
	# As of Nginx 1.7.5, add_header supports an "always" parameter which