Benjamin Barbe benjaminbarbe

When you build Erlang/OTP on OS X, it unfortunately defaults to handling a maximum of 1024 file descriptors. You can get around this limitation with the right combination of configuration options and manual changes to a generated config file.

First, go into your unpacked Erlang/OTP source directory and run the following command, replacing the value 10000 with whatever value you want for max file descriptors:

perl -i -pe 's/(define\s+FD_SETSIZE\s+)\d+/\1 10000/' erts/config.h.in

Next, when you run configure in your Erlang/OTP source directory, be sure to include the right CFLAGS setting, as shown below:

CFLAGS='-DREDEFINE_FD_SETSIZE -DFD_SETSIZE=15000 -D_DARWIN_UNLIMITED_SELECT' ./configure --enable-kernel-poll <other options>

How to write it : http://betterspecs.org/

rpsec helper methods : https://www.relishapp.com/rspec/rspec-core/docs/helper-methods/define-helper-methods-in-a-module

A screen cast Rspec/Capybara : http://railscasts.com/episodes/275-how-i-test

Capybara stuff : https://github.com/jnicklas/capybara

	#!/bin/bash

	# https://gist.github.com/949831
	# http://blog.carbonfive.com/2011/05/04/automated-ad-hoc-builds-using-xcode-4/

	# command line OTA distribution references and examples
	# http://nachbaur.com/blog/how-to-automate-your-iphone-app-builds-with-hudson
	# http://nachbaur.com/blog/building-ios-apps-for-over-the-air-adhoc-distribution
	# http://blog.octo.com/en/automating-over-the-air-deployment-for-iphone/
	# http://www.neat.io/posts/2010/10/27/automated-ota-ios-app-distribution.html

	#!/bin/bash -e
	#
	# Since unicorn creates a new pid on restart/reload, it needs a little extra love to
	# manage with runit. Instead of managing unicorn directly, we simply trap signal calls
	# to the service and redirect them to unicorn directly.
	#
	# To make this work properly with RVM, you should create a wrapper for the app's gemset unicorn.
	#

	function is_unicorn_alive {

	#!/usr/bin/ruby

	require 'rubygems'
	require 'aws-sdk'
	require 'erb'

	aws_email="email address here"
	aws_name="My Test Instance"

	# below is IAM credentials for my account

	user www-data;
	worker_processes 4;

	error_log /var/log/nginx/error.log;
	pid /var/run/nginx.pid;

	events {
	worker_connections 1024;
	}

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

	///
	var pkg = require("./package.json")
	, rimraf = require("rimraf")
	, gulp = require("gulp")
	, gutil = require("gulp-util")
	, filter = require("gulp-filter")
	, plumber = require("gulp-plumber")
	, concat = require("gulp-concat")

	gulp.task("clean", function() {

	/*

	gulpfile from one of my React applications which has a gulp --production build
	set up.

	Assumptions:

	1. All your own .js/.jsx modules are somewhere under ./src, have unique
	filenames and use Node.js-style requires WITHOUT any path information, just
	the name of another module somewhere under ./src

	module BaseEntity
	extend ActiveSupport::Concern

	include ActiveModel::Model
	include ActiveModel::Dirty
	include ActiveModel::Serializers::JSON
	include ActiveModel::Serializers::Xml

	included do
	include ::Virtus.model