Thomas Lee talee

On May 1, 2018, GitHub changed the suggested IP addresses to put on the A records for domains that use GitHub Pages. The new ones now support HTTPS for custom domains, but the old ones did not. Here are the old ones for historical purposes:

192.30.252.153
192.30.252.154

Here are the new ones:

185.199.108.153
185.199.109.153
185.199.110.153

gRPC Best Practice @ CoreOSFest 2017

https://coreosfest2017.sched.com/event/AWYc/best-practices-for-go-grpc-services-doug-fawley-google

Just small note for me. Hope the slide will be opened.

API design
- Idmpotency
  - It should be safe to retry an RPC without knowing whether it was processed
Example

openssl

Install

Install the OpenSSL on Debian based systems

sudo apt-get install openssl

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

	// see for screenshot:
	// https://twitter.com/paul_irish/status/829090506084749312

	const http = require('http');

	function requestHandler(request, response) {
	const headers = {
	'Server-Timing': `
	sql-1;desc="MySQL lookup Server";dur=100,
	sql-2;dur=900;desc="MySQL shard Server #1",

	import java.util.Set;
	import java.util.concurrent.ConcurrentHashMap;

	public class HelloCovariance {
	public static void main(String[] args) {
	ConcurrentHashMap<String, String> properties = new ConcurrentHashMap<>();
	Set<String> keySet = properties.keySet();
	}
	}

	'use strict';
	var gulp = require('gulp');
	var gutil = require('gulp-util');
	var del = require('del');
	var uglify = require('gulp-uglify');
	var gulpif = require('gulp-if');
	var exec = require('child_process').exec;


	var notify = require('gulp-notify');

	# taken from http://www.piware.de/2011/01/creating-an-https-server-in-python/
	# generate server.xml with the following command:
	# openssl req -new -x509 -keyout server.pem -out server.pem -days 365 -nodes
	# run as follows:
	# python simple-https-server.py
	# then in your browser, visit:
	# https://localhost:4443

	import BaseHTTPServer, SimpleHTTPServer
	import ssl

	###########################################
	# IMPORTANT NOTE:
	#
	# As of asuswrt-merlin 380.67 Beta, you
	# can now configure SSL certificates from
	# the Webui, making these instructions
	# unnecessary.
	###########################################

	# Installation
	brew install ffmpeg --with-vpx --with-vorbis --with-libvorbis --with-vpx --with-vorbis --with-theora --with-libogg --with-libvorbis --with-gpl --with-version3 --with-nonfree --with-postproc --with-libaacplus --with-libass --with-libcelt --with-libfaac --with-libfdk-aac --with-libfreetype --with-libmp3lame --with-libopencore-amrnb --with-libopencore-amrwb --with-libopenjpeg --with-openssl --with-libopus --with-libschroedinger --with-libspeex --with-libtheora --with-libvo-aacenc --with-libvorbis --with-libvpx --with-libx264 --with-libxvid

	# Easy Peasy
	ffmpeg -i video.mp4 video.webm