Pascal pascalpp

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

	//
	// UserDefaults.swift
	//
	// Created by Shaps Benkau on 24/05/2018.
	// Copyright © 2018 152percent Ltd. All rights reserved.
	//

	import Foundation

	#if os(iOS)

	/**
	* VH and VW units can cause issues on iOS devices: http://caniuse.com/#feat=viewport-units
	*
	* To overcome this, create media queries that target the width, height, and orientation of iOS devices.
	* It isn't optimal, but there is really no other way to solve the problem. In this example, I am fixing
	* the height of element `.foo` —which is a full width and height cover image.
	*
	* iOS Resolution Quick Reference: http://www.iosres.com/
	*/

	class Person {
	var name = ""
	var age = 0

	init(name: String, age:Int) {
	self.name = name
	self.age = age
	}
	}

	<!DOCTYPE html>
	<html lang="en">
	<head>
	<style>
	#my-carousel { border: 1px solid #000; padding: 10px; }
	.carousel-item { display: none; position: relative; padding: 0 30px;}
	.carousel-item .carousel-prev { position: absolute; left: 0; }
	.carousel-item .carousel-next { position: absolute; right: 0; }
	</style>
	</head>

	// This method gives you an easier way of calling super
	// when you're using Backbone in plain javascript.
	// It lets you avoid writing the constructor's name multiple
	// times. You still have to specify the name of the method.
	//
	// So instead of having to write:
	//
	// User = Backbone.Model.extend({
	// save: function(attrs) {
	// this.beforeSave(attrs);