Christian Klotz christianklotz

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

Channels Are Not Enough

... or Why Pipelining Is Not That Easy

Golang Concurrency Patterns for brave and smart.

By @kachayev

Intro

Golang Workers / Job Queue

A running example of the code from:

This gist creates a working example from blog post, and a alternate example using simple worker pool.

TLDR: if you want simple and controlled concurrency use a worker pool.

This is a proposal for a lightning talk at the Reactive 2015 conference.

NOTE: If you like this, star ⭐ the Gist - the amount of stars decides whether it makes the cut! You could also Retweet if you want :)

Pyramids be gone!

ES7 Async Functions

JavaScript is getting async functions (or already has them if you count Babel.JS) and with them a way to finally slay the evil pyramid. This new language feature lets you write asynchronous code that almost looks synchronous, while maintaining the same semantics as promises. This lets you shed your .then and .catch boilerplate and escape those nested callbacks in favour of clean, explicit, maintainable code.

	import Foundation

	/// An abstract class that makes building simple asynchronous operations easy.
	/// Subclasses must implement `execute()` to perform any work and call
	/// `finish()` when they are done. All `NSOperation` work will be handled
	/// automatically.
	open class AsynchronousOperation: Operation {

	// MARK: - Properties

	public typealias myFunctionDefAlias = (@objc_block (String, String, NSNumber) -> Void)

	@objc
	public protocol MyJSExportProtocol: JSExport {
	// JSExportAs alternative in Swift via closure
	var myFunction:myFunctionDefAlias? {get}
	}

	@objc
	public class MyJSExportClass: NSObject, MyJSExportProtocol {

	#!/bin/sh

	#
	# Forwards SSH agent into a Docker container running in the active
	# docker-machine
	#

	PROGNAME=$(basename $0)

	NAME=$(docker-machine active)

	---
	swagger: "2.0"
	basePath: "/test"
	schemes:
	- "https"
	paths:
	/lambdaredirect-default:
	get:
	produces:
	- "application/json"

	# The trick is to link the DeviceSupport folder from the beta to the stable version.
	# sudo needed if you run the Mac App Store version. Always download the dmg instead... you'll thank me later :)

	# Support iOS 15 devices (Xcode 13.0) with Xcode 12.5:
	sudo ln -s /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/15.0 /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport

	# Then restart Xcode and reconnect your devices. You will need to do that for every beta of future iOS versions

	# (A similar approach works for older versions too, just change the version number after DeviceSupport)

	import UIKit

	@UIApplicationMain
	class AppDelegate: UIResponder, UIApplicationDelegate {

	var window: UIWindow?

	func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {

	let window = UIWindow(frame: UIScreen.main.bounds)