swalkinshaw

Moved to Shopify/graphql-design-tutorial

chockenberry

#!/bin/sh

defaults read com.apple.finder CreateDesktop > /dev/null 2>&1
enabled=$?

if [ "$1" = "off" ]; then
	if [ $enabled -eq 1 ]; then
		defaults write com.apple.finder CreateDesktop false
		osascript -e 'tell application "Finder" to quit'
		open -a Finder

Stanback

#
# CORS header support
#
# One way to use this is by placing it into a file called "cors_support"
# under your Nginx configuration directory and placing the following
# statement inside your **location** block(s):
#
#   include cors_support;
#
# As of Nginx 1.7.5, add_header supports an "always" parameter which

jed

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

jmblog

/*-----------------------------------------------------
  960 Grid System ~ Core CSS.
  Learn more ~ http://960.gs/

  Licensed under GPL and MIT.
-------------------------------------------------------*/

/* Grid Settings
---------------------------*/
// 12-column grid