Jon Pierce jonpierce

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

OS X Screencast to animated GIF

This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.

Instructions

To capture the video (filesize: 19MB), using the free "QuickTime Player" application:

ruby-1.9.3-p327 cumulative performance patch for rbenv

This installs a patched ruby 1.9.3-p327 with various performance improvements and a backported COW-friendly GC, all courtesy of funny-falcon.

Requirements

You will also need a C Compiler. If you're on Linux, you probably already have one or know how to install one. On OS X, you should install XCode, and brew install autoconf using homebrew.

	Notes from my talk are here:
	https://gist.github.com/3935383

	"Doing crazy stuff in redis" - Fitzy @fritzy from &Yet
	* Everything on the internet is feeds in feeds, your follower list, your status updates..
	* XMPP pubsub interface, called ZUMP, was XEP60.. it "kinda sucked" and "was really slow"
	* I wanted something that fans out messages and was fast and if only there was something that already did that -- well they did, and it was redis.
	* Implemented XEP60 in redis, and it was fast and awesome. "And then I had an epiphany"
	* "I didn't need XMPP, this could be useful for ANY API..." events, and publishing messages could be useful for all the apis. "I know some of you JavaScripters think there's just HTTP, but there is a whole world of Protocols and APIs that could benefit."
	* "What if we had CRUD events that came out of custom objects that weren't just feeds?"

	Redis Pain - Matt @mranney from Voxer (did node-redis)
	* Asked to talk about redis stress points.. "no stress, things work for a while and there is no stress and then... you enter a world of pain."
	* Pain from how we use it at Voxer. Explanation of Voxer and its use cases.
	* People assume Voxer is "how hard can it be?".. "That's how it used to be until we got a bunch of pictures..."
	* Growth curve looks like Pinterests "might be the same because there was no label on the y-axis.. might be EXACTLY the same."
	* Computers are hard... nothing works as it is supposed to... and eventually you fly into nerd rage and then you become a curmmudgeon... getting serious, this isn't real pain -- we aren't selling stree sheets -- this are great problems to have...
	* They use redis as cache for Riak, also for rapidly changing data, "data we can afford to lose", throttling, NO SAVING.
	* "We really like redis."
	* "When we first started building voxer, I never understood why people use Redis at all... we have a db and .

	Lightning talk: BigCache:
	* redis distributed fault-tolerant memory cache as a service (OSS)
	* memcache binary protocol compatible
	* TCP loadbalanced / consistent hashing algo, ZK for coordination services
	* github.com/mercadolibre/bigcache


	EvilSha: misadventures in the land of lua. Adam Baldwin: @adam_baldwin
	* What can we do that is evil with Redis?
	* Listed all functions you have access to in lua in redis; pretty locked-down

	Dr Josiah Carlson
	- Redis user for 2 1/2 years. Extremely active on redis mailing list, #3 poster to the list (applause from PN)
	- Author of Redis In Action (available electronically)
	- What is search? scan text, use BM/BMG/KMP or regex or recursive-descent.. or suffix tries.. or you can search through the zip-format (BWT)
	- Inverted index: words to documents, instead of crawling documents for words.
	- SET per word with items for each docid, using redis' intersection for AND, union for OR
	- "Simplest example that will be useful..[but it wont be that useful... buy the book!]"
	- Demo of his editor.. its on sourceforge.
	- Tokenization, stop words in some python code.. "with this stuff, we're going to implement search" already has failing tests written.. live coding, so not many notes... buy his book.
	- "I have 5 minutes? I thought this was a 45-minute talk".. "Nope!"..."Shoot!"

	Redisconf Notes:

	"We will begin this morning with a performance"
	"Is this a key store..." Bohemian Rhapsody Key/Value Store ballad. Epic Win!
	"Any way the data flows doesn't really matter to me... flushdb..."
	"Lua killed a db by writing after calling a nondeterministic function..."
	"Got to leave SQL behind and face the truth..."
	"Redis, I don't want to join, sometimes I wish I'd never described a query..."
	"The ZSET has some data set aside for me, for me, for MEEEEEEE"

	- (BOOL)webView:(UIWebView )webView shouldStartLoadWithRequest:(NSURLRequest )request
	navigationType:(UIWebViewNavigationType)navigationType {
	NSString *urlString = [[request URL] absoluteString];

	if ([urlString hasPrefix:@"js:"]) {
	NSString *jsonString = [[[urlString componentsSeparatedByString:@"js:"] lastObject]
	stringByReplacingPercentEscapes];
	NSData *jsonData = [jsonString dataUsingEncoding:NSUTF8StringEncoding];

	NSError *error;

	Hi!