sh3b

-Step 1: basic HTML skeleton for a full-screen map
-Step 2: initialize a map
-Step 3: add a tile layer
-Step 4: Add a marker
-Step 5: Add a line
-Step 6: Add a polygon
-Step 7: Styling: add a polygon with different styling
-Step 8: Click/hover
   -On click, re-center map
   -On hover, change styling of polygon

sh3b

[mike.tig.as][mta] server configuration

This gist contains the nginx and tor configurations for the [mike.tig.as][mta] servers, mainly to show:

• Use of the chris-lea/nginx-devel PPA to allow use of SPDY.
• ssl_ciphers selection to mitigate BEAST attack, enable [perfect forward secrecy][pfs] if possible and select the strongest possible ciphers within those bounds. (Exception is made for several ciphers at the end of list, for compatibility reasons.)

sh3b

Client-side SSL

For excessively paranoid client authentication.

Using self-signed certificate.

Create a Certificate Authority root (which represents this server)

Organization & Common Name: Some human identifier for this server CA.

openssl genrsa -des3 -out ca.key 4096
openssl req -new -x509 -days 365 -key ca.key -out ca.crt

sh3b

# This configuration file is provided on an "as is" basis,
# with no warranties or representations, and any use of it
# is at the user's own risk.
#
# You will need to edit domain name information, IP addresses for redirection (at the bottom),
# SSL certificate and key paths, and the "Public-Key-Pins" header.

user www-data;
worker_processes 4;
pid /run/nginx.pid;

sh3b

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

sh3b

server {
            listen 80;
            server_name cloud.domain.net;
            return 301 https://$server_name$request_uri;  # enforce https
}

server {
        listen 443 ssl spdy;

        gzip off;        

sh3b

In a perfect world, where things are done well, not just quickly, I would expect to find the following when joining the company:

Documentation

• Accurate / up-to-date systems architecture diagram

• Accurate / up-to-date network diagram

• Out-of-hours support plan

• Incident management plan

sh3b

# Default options for sslh initscript
# sourced by /etc/init.d/sslh

# Disabled by default, to force yourself
# to read the configuration:
# - /usr/share/doc/sslh/README.Debian (quick start)
# - /usr/share/doc/sslh/README, at "Configuration" section
# - sslh(8) via "man sslh" for more configuration details.
# Once configuration ready, you *must* set RUN to yes here
# and try to start sslh (standalone mode only)

sh3b

#!/bin/sh

ls Postman*.tar.gz > /dev/null 2>&1
if [ $? -eq 0 ]; then
	echo "Removing old Postman tarballs"
	rm -f $(ls Postman*.tar.gz)
fi

curlExists=$(command -v curl)