Grégory Horion gregory

ruby-1.9.3-p327 cumulative performance patch for rbenv

This installs a patched ruby 1.9.3-p327 with various performance improvements and a backported COW-friendly GC, all courtesy of funny-falcon.

Requirements

You will also need a C Compiler. If you're on Linux, you probably already have one or know how to install one. On OS X, you should install XCode, and brew install autoconf using homebrew.

Google Speech To Text API

Base URL: https://www.google.com/speech-api/v1/recognize
It accepts POST requests with voice file encoded in FLAC format, and query parameters for control.

Query Parameters

client
The client's name you're connecting from. For spoofing purposes, let's use chromium

lang
Speech language, for example, ar-QA for Qatari Arabic, or en-US for U.S. English

Examples of RESTful API calls for E-commerce platforms

These examples are type 3 RESTful API requests and responses. The JSON-HAL specification is used to implement HATEOAS.

Some of the examples are based on my work as architect of the RESTful API at http://www.hautelook.com. All proprietary information has been removed.

Relevant links

JSON-HAL specification: http://stateless.co/hal_specification.html#media_type_identifiers
JSON linking with HAL: http://blog.stateless.co/post/13296666138/json-linking-with-hal

	require 'rest_client'
	require 'json'
	a = `sox -d --norm -t .flac - silence -l 1 0 1% 1 6.0 1% rate 16k`
	#a = `arecord -q -d 3 -c 1 -f S16_LE -r 22050 -t wav \| flac - -f --totally-silent -o-`
	r = RestClient.post 'https://www.google.com/speech-api/v1/recognize?lang=en-US', a,
	:content_type => 'audio/x-flac; rate=16000'
	if j = JSON.parse(r)
	(p j; `espeak 'you said: #{j['hypotheses'].first['utterance']}'`)
	end

	https://www.pivotaltracker.com/help/api?version=v3#github_hooks
	https://www.pivotaltracker.com/help/api?version=v3#scm_post_commit_message_syntax

	SCM Post-Commit Message Syntax

	To associate an SCM commit with a specific Tracker story, you must include a special syntax in the commit message to indicate one or more story IDs and (optionally) a state change for the story. Your commit message should have square brackets containing a hash mark followed by the story ID. If a story was not already started (it was in the "not started" state), a commit message will automatically start it. For example, if Scotty uses the following message when committing SCM revision 54321:

	[#12345677 #12345678] Diverting power from warp drive to torpedoes.

	// in new iframe

	var whitelist = {
	// add whitelisted globals
	};

	var handler = {
	// Fundamental traps
	getOwnPropertyDescriptor: function(name) {
	var desc = Object.getOwnPropertyDescriptor(whitelist, name);

	#This is the "site config" for nginx

	upstream django {
	# Distribute requests to servers based on client IP. This keeps load
	# balancing fair but consistent per-client. In this instance we're
	# only using one uWGSI worker anyway.
	ip_hash;
	server unix:/tmp/uwsgi.sock;
	}
	server {

	/**
	* Module dependencies.
	*/

	var express = require('express')
	, routes = require('./routes')
	, cluster = require('cluster');

	var app = module.exports = express.createServer()
	, io = require('./socket')(app);

	#!/bin/bash
	# herein we backup our indexes! this script should run at like 6pm or something, after logstash
	# rotates to a new ES index and theres no new data coming in to the old one. we grab metadatas,
	# compress the data files, create a restore script, and push it all up to S3.
	TODAY=`date +"%Y.%m.%d"`
	INDEXNAME="logstash-$TODAY" # this had better match the index name in ES
	INDEXDIR="/usr/local/elasticsearch/data/logstash/nodes/0/indices/"
	BACKUPCMD="/usr/local/backupTools/s3cmd --config=/usr/local/backupTools/s3cfg put"
	BACKUPDIR="/mnt/es-backups/"
	YEARMONTH=`date +"%Y-%m"`

	# MOTIVATION: As rails apps are growing, people are noticing the drawbacks
	# of the ActiveRecord pattern. Several apps I have seen, and several
	# developers I have spoken to are looking towards other patterns for object
	# persistence. The major drawback with ActiveRecord is that the notion
	# of the domain object is conflated with what it means to store/retrieve
	# it in any given format (like sql, json, key/value, etc).
	#
	# This is an attempt to codify the Repository pattern in a way that would
	# feel comfortable to beginner and seasoned Ruby developers alike.
	#