Chris Watson cwonrails

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I lead the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can'

Contract Killer

The popular open-source contract for web professionals by Stuff & Nonsense

Originally published: 23rd December 2008
Revised date: March 15th 2016
Original post

The spec has moved to a repo: https://github.com/defunctzombie/package-browser-field-spec to facilitate collaboration.

Let's Encrypt on Ubuntu 14.04, nginx with webroot auth

This document details how I setup LE on my server. Firstly, install the client as described on http://letsencrypt.readthedocs.org/en/latest/using.html and make sure you can execute it. I put it in /root/letsencrypt.

As it is not possible to change the ports used for the standalone authenticator and I already have a nginx running on port 80/443, I opted to use the webroot method for each of my domains (note that LE does not issue wildcard certificates by design, so you probably want to get a cert for www.example.com and example.com).

Configuration

For this, I placed config files into etc/letsencrypt/configs, named after <domain>.conf. The files are simple:

	/*
	\|--------------------------------------------------------------------------
	\| Browser-sync config file
	\|--------------------------------------------------------------------------
	\|
	\| Please report any issues you encounter:
	\| https://github.com/shakyShane/browser-sync/issues
	\|
	\| For up-to-date information about the options:
	\| https://github.com/shakyShane/browser-sync/wiki/Working-with-a-Config-File

	/**
	*
	* Hooking up Watchify with Google's Web Starter Kit
	*
	* The primary use cases for Browserify/Watchify are:
	* - Node.js-style `require`s on the client-side
	* - Use of npm modules on the client-side
	* - No more new <script> tags for each new script/module
	*
	* 1. npm install --save-dev vinyl-source-stream browserify watchify gulp-notify

	'use strict';

	// Include Gulp & Tools We'll Use
	var gulp = require('gulp');
	var $ = require('gulp-load-plugins')();
	var del = require('del');
	var runSequence = require('run-sequence');
	var browserSync = require('browser-sync');
	var pagespeed = require('psi');
	var reload = browserSync.reload;

	daemon off;

	user nginx;
	worker_processes 1;

	pid /var/run/nginx.pid;

	events {
	worker_connections 1024;
	}

	var gulp = require('gulp'),
	// Used to process `include` statements in source files
	includer = require('gulp-includer'),
	// Compiles SASS files using LibSass
	sass = require('gulp-sass'),
	// Renames files in the file stream
	rename = require('gulp-rename'),
	// JavaScript minifier
	uglify = require('gulp-uglify'),
	// Filter files out of the vinyl stream

	# Automatically instal the latest nginx
	wget -O - http://nginx.org/keys/nginx_signing.key \| sudo apt-key add -

	#Make a backup copy of your current sources.list file
	sudo cp /etc/apt/sources.list /etc/apt/sources.list.bak

	#Now copy the following repositories to the end of ` /etc/apt/sources.list`
	echo "deb http://nginx.org/packages/mainline/ubuntu/ trusty nginx" \| sudo tee -a /etc/apt/sources.list
	echo "deb-src http://nginx.org/packages/mainline/ubuntu/ trusty nginx" \| sudo tee -a /etc/apt/sources.list