tåmm¥ dreadwarrior

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

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

DDD, CQRS and Event Sourcing in PHP

Broadway - Infrastructure and testing helpers for creating CQRS and event sourced applications
EventCentric.Core - Event Sourcing and CQRS in PHP
LiteCQRS - Small convention based CQRS library for PHP
predaddy - Common DDD classes including an annotation driven message bus and tools for CQRS and Event Sourcing
ProophEventSourcing - Provides basic functionality for event-sourced aggregates
ProophEventStore - PHP 5.4+ EventStore Implementation
ProophServiceBus - PHP Enterprise Service Bus Implementation supporting CQRS and DDD

TYPO3 Dynamic Return Type code completion

When using PhpStorm:

install DynamicReturnTypePlugin from http://plugins.jetbrains.com/plugin/7251?pr=phpStorm&showAllUpdates=true
add dynamicReturnTypeMeta.json to your TYPO3 CMS project root
live a better life

You're welcome, you owe me a beer.

	SQL:
	images int(11) unsigned DEFAULT '0',
	=======================================================
	TCA
	....
	'images' => array(
	'exclude' => 0,
	'label' => 'images',
	'config' => \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::getFileFieldTCAConfig(
	'images',

	(function() {
	var CSSCriticalPath = function(w, d, opts) {
	var opt = opts \|\| {};
	var css = {};
	var pushCSS = function(r) {
	if(!!css[r.selectorText] === false) css[r.selectorText] = {};
	var styles = r.style.cssText.split(/;(?![A-Za-z0-9])/);
	for(var i = 0; i < styles.length; i++) {
	if(!!styles[i] === false) continue;
	var pair = styles[i].split(": ");

	#!/usr/bin/env bash
	# script: watch
	# author: Mike Smullin <[email protected]>
	# license: GPLv3
	# description:
	# watches the given path for changes
	# and executes a given command when changes occur
	# usage:
	# watch <path> <cmd...>
	#

	#!/bin/bash

	##
	## Simple logging mechanism for Bash
	##
	## Author: Michael Wayne Goodman <[email protected]>
	## Thanks: Jul for the idea to add a datestring. See:
	## http://www.goodmami.org/2011/07/simple-logging-in-bash-scripts/#comment-5854
	## Thanks: @gffhcks for noting that inf() and debug() should be swapped,
	## and that critical() used $2 instead of $1

	#!/bin/bash

	# Usage:
	#
	# cat file.yml \| load-yaml-dump-json
	# ./load-yaml-dump-json # enter data and ctl-d when finished

	yaml=`cat`

	echo == Perl

	<?php
	function it($m,$p){echo ($p?'✔︎':'✘')." It $m\n"; if(!$p){$GLOBALS['f']=1;}}function done(){if(@$GLOBALS['f'])die(1);}