Harry Dobrev hkdobrev

I have spent quite a bit of time figuring out automounts of NFS shares in OS X...

Somewhere along the line, Apple decided allowing mounts directly into /Volumes should not be possible:

/etc/auto_master (see last line):

#
# Automounter master map
#

+auto_master # Use directory service

Plain Strings (207): foo
Anchors (208): k$
Ranges (202): ^[a-f]*$
Backrefs (201): (...).*\1
Abba (169): ^(.(?!(ll|ss|mm|rr|tt|ff|cc|bb)))*$|^n|ef
A man, a plan (177): ^(.)[^p].*\1$
Prime (286): ^(?!(..+)\1+$)
Four (199): (.)(.\1){3}
Order (198): ^[^o].....?$
Triples (507): (^39|^44)|(^([0369]|([147][0369]*[258])|(([258]|[147][0369]*[147])([0369]*|[258][0369]*[147])([147]|[258][0369]*[258])))*$)

Selections and Multiple Cursors in Sublime Text 3

A handy list of selection shortcuts.

Here are the official docs: Keyboard and Mouse

Mouse

Building blocks:

Add to selection: Ctrl
Subtract from selection: Alt

a simple git branching model (written in 2013)

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

Update: Woah, thanks for all the attention. Didn't expect this simple rant to get popular.

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

	# Compiled source #
	###################
	*.com
	*.class
	*.dll
	*.exe
	*.o
	*.so

	# Packages #

	<?php namespace Vendor\Library;

	use Another\Vendor\Library\ClassName;

	abstract class ClassName extends AnotherClass implements Countable, Serializable
	{
	const CONSTANTS = 'top';

	use someTrait, anotherTrait {
	anotherTrait::traitMethod insteadof someTrait;

	SELECT id,state,command,time,left(replace(info,'\n','<lf>'),120)
	FROM information_schema.processlist
	WHERE command <> 'Sleep'
	AND info NOT LIKE '%PROCESSLIST%'
	ORDER BY time DESC LIMIT 50;

	module.exports = function (grunt) {
	// show elapsed time at the end
	require('time-grunt')(grunt);
	// load all grunt tasks
	require('load-grunt-tasks')(grunt);

	//MODIFIED: add require for connect-modewrite
	var modRewrite = require('connect-modrewrite');

	grunt.initConfig({

	#
	# 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