Zhennan LI nanmu42

The introduction to Reactive Programming you've been missing

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

To install tcptraceroute on Debian/Ubuntu:

$ sudo apt-get install tcptraceroute

To install tcptraceroute on CentOS/REHL, first set up RepoForge on your system, and then:

$ sudo yum install tcptraceroute

Encoding Video

Installing

Install FFmpeg with homebrew. You'll need to install it with a couple flags for webm and the AAC audio codec.

brew install ffmpeg --with-libvpx --with-libvorbis --with-fdk-aac --with-opus

Virtualenv Cheatsheet

Create a virtualenv
```
$ virtualenv env
```
Activate

go run -ldflags "-s \
  -X main.Version=1.0.2 \
  -X main.BuildTime=`TZ=UTC date -u '+%Y-%m-%dT%H:%M:%SZ'` \
  -X main.GitHash=`git rev-parse HEAD`" \
  myapp.go

Adopted from www.atatus.com

Some of the Redis best practices content has moved

This content from this markdown file has moved a new, happier home where it can serve more people. Please check it out : https://docs.microsoft.com/azure/azure-cache-for-redis/cache-best-practices.

NOTE: Client specific guidance listed below is still valid and should still be considered. I will update this document once all content has been moved.

Why?

Useful for:

updating current terminal's shell env proxy settings, or
wrapping exec in .desktop files to inject env proxy settings

GNOME proxy settings should normally get propergated into the shell (bash) environment via gnome-terminal, e.g. http_proxy and no_proxy. However:

I noticed that applications exectuted via .desktop entries sometimes don't work. This happens when an app ignores org.gnome.proxy settings but can often use proxy env vars from the shell.
If you're proxy settings change, existing shell processes will still have the old proxy enviroment variables, so this can help refresh them whithout having to create a new shell.

	This demonstrates how to make client side certificates with go

	First generate the certificates with

	./makecert.sh [email protected]

	Run the server in one terminal

	go run server.go

	package main

	import (
	"fmt"
	"log"
	"net"
	"net/mail"
	"net/smtp"
	"crypto/tls"
	)

	#!/usr/bin/env bash
	#
	# Generate a set of TLS credentials that can be used to run development mode.
	#
	# Based on script by Ash Wilson (@smashwilson)
	# https://github.com/cloudpipe/cloudpipe/pull/45/files#diff-15
	#
	# usage: sh ./genkeys.sh NAME HOSTNAME IP

	set -o errexit