Di Wu wudi

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

Benchmarking Nginx with Go

There are a lot of ways to serve a Go HTTP application. The best choices depend on each use case. Currently nginx looks to be the standard web server for every new project even though there are other great web servers as well. However, how much is the overhead of serving a Go application behind an nginx server? Do we need some nginx features (vhosts, load balancing, cache, etc) or can you serve directly from Go? If you need nginx, what is the fastest connection mechanism? This are the kind of questions I'm intended to answer here. The purpose of this benchmark is not to tell that Go is faster or slower than nginx. That would be stupid.

So, these are the different settings we are going to compare:

Go HTTP standalone (as the control group)
Nginx proxy to Go HTTP
Nginx fastcgi to Go TCP FastCGI
Nginx fastcgi to Go Unix Socket FastCGI

集群

CLUSTER INFO 打印集群的信息

CLUSTER NODES 列出集群当前已知的所有节点（node），以及这些节点的相关信息。

	//
	// Regular Expression for URL validation
	//
	// Author: Diego Perini
	// Created: 2010/12/05
	// Updated: 2018/09/12
	// License: MIT
	//
	// Copyright (c) 2010-2018 Diego Perini (http://www.iport.it)
	//

	server {
	root /var/www/example.com/static;
	server_name example.com;
	access_log /var/log/nginx/example.com.access.log;
	error_log /var/log/nginx/example.com.error.log;

	try_files /maintenance.html @proxy;

	location @proxy {
	proxy_pass http://127.0.0.1:10001;

	# Makefile for a go project
	#
	# Author: Jon Eisen
	# site: joneisen.me
	#
	# Targets:
	# all: Builds the code
	# build: Builds the code
	# fmt: Formats the source files
	# clean: cleans the code

	# Start by checking if they fixed it upstream:

	brew update
	brew upgrade reattach-to-user-namespace

	# If it says it's already installed, they haven't fixed it upstream. So do this:

	# Edit the recipe:
	brew edit reattach-to-user-namespace

	/*
	Copyright (c) 2017 Chris Patuzzo
	https://twitter.com/chrispatuzzo

	Permission is hereby granted, free of charge, to any person obtaining a copy
	of this software and associated documentation files (the "Software"), to deal
	in the Software without restriction, including without limitation the rights
	to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
	copies of the Software, and to permit persons to whom the Software is
	furnished to do so, subject to the following conditions:


	0 = Success
	1 = Operation not permitted
	2 = No such file or directory
	3 = No such process
	4 = Interrupted system call
	5 = Input/output error
	6 = No such device or address
	7 = Argument list too long
	8 = Exec format error

	[global]
	# TDS protocol version
	tds version = 7.0
	client charset = UTF-8