Benjamin Oertel boertel

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

Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.

Discussion on reddit.

Python 2.x

$ python -m SimpleHTTPServer 8000

This is now an actual repo:

https://github.com/cowboy/jquery-tiny-pubsub

	#
	# Working with branches
	#

	# Get the current branch name (not so useful in itself, but used in
	# other aliases)
	branch-name = "!git rev-parse --abbrev-ref HEAD"
	# Push the current branch to the remote "origin", and set it to track
	# the upstream branch
	publish = "!git push -u origin $(git branch-name)"

	license: gpl-3.0
	height: 600
	border: no
	redirect: https://observablehq.com/@d3/d3-hexbin-map

	/*
	I've never been a fan of JavaScript frameworks.
	These three functions are all I ever really need!
	*/

	/* convenient DOM element lookup */
	function $(el){
	return document.getElementById(el);
	}

	//Download jquery.js and place it in the build, do not use require-jquery.js
	//in the build, since each of the build layers just needs almond and not the
	//full require.js file.
	//This file is run in nodejs to do the build: node build.js

	//Load the requirejs optimizer
	var requirejs = require('./r.js');

	//Set up basic config, include config that is
	//common to all the requirejs.optimize() calls.