henrik

tmux cheatsheet

As configured in my dotfiles.

start new:

tmux

start new with session name:

jexchan

Multiple SSH Keys settings for different github account

create different public key

create different ssh key according the article Mac Set-Up Git

$ ssh-keygen -t rsa -C "[email protected]"

MohamedAlaa

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

cespare

type ApacheLogRecord struct {
	http.ResponseWriter

	ip                    string
	time                  time.Time
	method, uri, protocol string
	status                int
	responseBytes         int64
	elapsedTime           time.Duration
}

louiszuckerman

#!/bin/bash
 
if [[ "$#" < "2" || "$#" > "3" ]]; then
  cat <<END
Glusterfs GFID resolver -- turns a GFID into a real file path
 
Usage: $0 <brick-path> <gfid> [-q]

  <brick-path> : the path to your glusterfs brick (required)
  

sinkers

import re
import subprocess
import logging
import math
import json
import pygal
import sys
logger = logging.getLogger(__name__)

'''

denji

Moved to git repository: https://github.com/denji/golang-tls

Generate private key (.key)

# Key considerations for algorithm "RSA" ≥ 2048-bit
openssl genrsa -out server.key 2048

# Key considerations for algorithm "ECDSA" ≥ secp384r1
# List ECDSA the supported curves (openssl ecparam -list_curves)

harlow

Golang Workers / Job Queue

A running example of the code from:

• http://marcio.io/2015/07/handling-1-million-requests-per-minute-with-golang
• http://nesv.github.io/golang/2014/02/25/worker-queues-in-go.html

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.

andrewmkhoury

AEM6.x Migration

• How to Rebuild a Pre-Existing AEM+Mongo Cluster
• or migrate from Tar to MongoDB or MongoDB to Tar"
• or migrate from 5.6.1 or 6.x to 6.x via data migration instead of jar upgrade

1. (Mongo to Mongo only) Remove one replica from the replica set and delete/recreate the db
   1. Remove the replica node from the set: http://docs.mongodb.org/master/tutorial/remove-replica-set-member/
   2. Validate that no other nodes in the set consider that node to be part of the set anymore. Log into each node in the cluster via mongo shell and run rs.status() to validate that the node that was taken out is not in the cluster any longer.
   3. Drop the aem database on that node http://docs.mongodb.org/manual/reference/command/dropDatabase/
2. Re-add the database with the correct user permissions (do not add the mongo instance back to the replica set)

mutin-sa

Google Public NTP [AS15169]:

time.google.com

time1.google.com

time2.google.com

time3.google.com