Gabriel Francisco fgbreel

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

Update May 2017

Eric Bidelman has documented some of the common workflows possible with headless Chrome over in https://developers.google.com/web/updates/2017/04/headless-chrome.

Update

If you're looking at this in 2016 and beyond, I strongly recommend investigating real headless Chrome: https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md

Windows and Mac users might find using Justin Ribeiro's Docker setup useful here while full support for these platforms is being worked out.

	// Just before switching jobs:
	// Add one of these.
	// Preferably into the same commit where you do a large merge.
	//
	// This started as a tweet with a joke of "C++ pro-tip: #define private public",
	// and then it quickly escalated into more and more evil suggestions.
	// I've tried to capture interesting suggestions here.
	//
	// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_,
	// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant,

	# Postfix stuff based on https://gist.github.com/jbrownsc/4694374:

	QUEUEID (?:[A-F0-9]+\|NOQUEUE)
	EMAILADDRESSPART [a-zA-Z0-9_.+-=:]+
	EMAILADDRESS %{EMAILADDRESSPART:local}@%{EMAILADDRESSPART:remote}
	RELAY (?:%{HOSTNAME:relayhost}(?:\[%{IP:relayip}\](?::[0-9]+(.[0-9]+)?)?)?)
	POSREAL [0-9]+(.[0-9]+)?
	DELAYS (%{POSREAL}[/]*)+
	DSN %{NONNEGINT}.%{NONNEGINT}.%{NONNEGINT}
	STATUS sent\|deferred\|bounced\|expired

	apply plugin: 'java'
	apply plugin : 'war'

	group = 'com.cadrlife'
	version = '1.0.0'

	buildscript {
	repositories {
	mavenCentral()
	}

	#!/usr/bin/env bash

	# Simple move this file into your Rails `script` folder. Also make sure you `chmod +x puma.sh`.
	# Please modify the CONSTANT variables to fit your configurations.

	# The script will start with config set by $PUMA_CONFIG_FILE by default

	PUMA_CONFIG_FILE=config/puma.rb
	PUMA_PID_FILE=tmp/pids/puma.pid
	PUMA_SOCKET=tmp/sockets/puma.sock

	#!/usr/bin/env python
	# -- coding: utf-8 --


	def archive_to_bytes(archive):
	def to_seconds(s):
	SECONDS_IN_A = {
	's': 1,
	'm': 1 * 60,
	'h': 1 * 60 * 60,

	if [ ! -f /tmp/.X5-lock ]; then /usr/bin/Xvfb :5 -ac -screen 0 1024x768x8 & fi
	export DISPLAY=:5.0 # firefox needs this to know where to find a display to run on
	java -jar /opt/selenium/selenium-server-standalone-2.26.0.jar > /dev/null 2>&1 &

	#!/usr/bin/env ruby

	#------------------------------------------------------------------------------
	# Aggregate Print useful information from /proc/[pid]/smaps
	#
	# pss - Roughly the amount of memory that is "really" being used by the pid
	# swap - Amount of swap this process is currently using
	#
	# Reference:
	# http://www.mjmwired.net/kernel/Documentation/filesystems/proc.txt#361

	# _utils.sh --- Utilities used across all the scripts.

	set -e
	set -o pipefail

	# Prints spaces as a prefix to the command's output.
	function prefixed {
	sed -e "s/^/ /"
	}