Raul Murciano raul

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying

one
two

Some text...

$ foo bar

	A backup of http://sites.google.com/site/redcodenl/creating-shazam-in-java-1 just in case
	Why is this necessary? Read http://sites.google.com/site/redcodenl/patent-infringement
	Please fork, tweet about, etc.
	----


	Creating Shazam in Java
	A couple of days ago I encountered this article: How Shazam Works

	This got me interested in how a program like Shazam works… And more importantly, how hard is it to program something similar in Java?

	#----------------------------------------------------------------------------
	# Git Setup
	#----------------------------------------------------------------------------
	file '.gitignore', <<-FILE
	.DS_Store
	log/*.log
	tmp/*/
	config/database.yml
	db/*.sqlite3
	public/uploads/*

	# Adapted for Rspec2. This won't work in RSpec 1.
	# Put this code in acceptance_helper.rb or better in a new file spec/acceptance/support/javascript.rb

	Rspec.configure do \|config\|

	config.before(:each) do
	Capybara.current_driver = :selenium if example.metadata[:js]
	end

	config.after(:each) do

	var detectBackOrForward = function(onBack, onForward) {
	hashHistory = [window.location.hash];
	historyLength = window.history.length;

	return function() {
	var hash = window.location.hash, length = window.history.length;
	if (hashHistory.length && historyLength == length) {
	if (hashHistory[hashHistory.length - 2] == hash) {
	hashHistory = hashHistory.slice(0, -1);
	onBack();

	#!/usr/bin/env ruby

	#
	# Joins paragraphs so that they span one long line.
	# Quoted or indented text are left untouched.
	# Useful for Gmail.
	#
	open('\| pbcopy', 'w') do \|pbcopy\|
	pbcopy.write(`pbpaste`.gsub(/([^>\n])\n(\w)/, '\\1 \\2'))
	end

	<!doctype html>
	<html lang=en>
	<head>
	<title>quick'n'dirty js testing framework</title>
	<meta charset=utf-8>
	<style type="text/css" media="screen">
	p { font: .8em courier; padding: .5em 1em; margin: 0;}
	.pass { color: #4F8A10; background: #DFF2BF }
	.fail { color: #D8000C; background: #FFBABA }
	.error{ color: white; background: red }

	#!/usr/bin/env bash
	curl https://s3.amazonaws.com/heroku-jvm-buildpack-vi/vim-7.3.tar.gz --output vim.tar.gz
	mkdir vim && tar xzvf vim.tar.gz -C vim
	export PATH=$PATH:/app/vim/bin

	namespace :fastly do

	desc "set fastly cors headers to fix chrome/firefox font loading issues"
	task allow_cors: :environment do

	# check for the Cors Allow header

	versions = Yajl.load(Excon.get("https://api.fastly.com/service/#{ENV['FASTLY_SERVICE_ID']}/version",
	:headers => {'Fastly-Key'=>ENV['FASTLY_API_KEY']}).body)
	last_version = versions.last['number']