Niclas Mietz solidnerd

## latency.markdown

      
              2 files
            
          
              742 forks
            
          
              49 comments
            
          
              4385 stars
            
          
                hellerbarde
                / latency.markdown
            
            
              Created
              May 31, 2012 13:16
                — forked from jboner/latency.txt
            
              
                Latency numbers every programmer should know
              
          
    Latency numbers every programmer should know

L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns             
Compress 1K bytes with Zippy ............. 3,000 ns  =   3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns  =  20 µs
SSD random read ........................ 150,000 ns  = 150 µs

Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs

  
## docker_cheat.md

      
              1 file
            
          
              146 forks
            
          
              33 comments
            
          
              903 stars
            
          
                wsargent
                / docker_cheat.md
            
            
              Last active
              August 31, 2023 12:10
            
              
                Docker cheat sheet
              
          
    303 See Other

Location: https://github.com/wsargent/docker-cheat-sheet

Hi there!
The docker cheat sheet has moved to a Github project under https://github.com/wsargent/docker-cheat-sheet.
Please click on the link above to go to the cheat sheet.

  
## install_elixir.md

      
              1 file
            
          
              50 forks
            
          
              5 comments
            
          
              159 stars
            
          
                rubencaro
                / install_elixir.md
            
            
              Last active
              September 30, 2023 03:58
            
              
                Elixir installation guide
              
          
    Elixir installation guide

Version numbers should be the ones you want. Here I do it with the last ones available at the moment of writing.
The simplest way to install elixir is using your package manager. Sadly, at the time of writing only Fedora shows
the intention to keep its packages up to date. There you can simply sudo dnf install erlang elixir and you are good to go.
Anyway, if you intend to work with several versions of erlang or elixir at the same time, or you are tied to
a specific version, you will need to compile it yourself. Then asdf is your best friend.

  
## autopart.sh
#!/bin/bash

# An set of disks to ignore from partitioning and formatting
BLACKLIST="/dev/sda|/dev/sdb"
# Base directory to hold the data* files
DATA_BASE="/media"

usage() {
    echo "Usage: $(basename $0) <new disk>"
}

## README-Template.md

      
              1 file
            
          
              4763 forks
            
          
              1701 comments
            
          
              13991 stars
            
          
                PurpleBooth
                / README-Template.md
            
            
              Last active
              May 3, 2024 18:53
            
              
                A template to make good README.md
              
          
    Project Title

One Paragraph of project description goes here
Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
Prerequisites


## README.md

      
              1 file
            
          
              12 forks
            
          
              0 comments
            
          
              40 stars
            
          
                twolfson
                / README.md
            
            
              Last active
              January 22, 2024 07:32
            
              
                Setting up SOPS
              
          
    I'm learning about SOPS and setting it up as my preferred mechanism for storing secrets. Here are my notes.
PGP

It’s security mechanism is that we (i.e. client) use a PUBLIC key from the receiver (i.e. server) and encode it with a random key (I’m saying nonce but it could be reused)
This varies from RSA and SSH because the server uses a PUBLIC key to identify the client.
Web of trust

Web of trust operates by still using PGP (i.e. encoding with recipient’s public key) but additionally, we can encrypt/sign the data as our own by signing it with the client’s private key.
This means the recipient will initially decrypt via our (i.e. client’s) public key (verifying the source) and then decrypting via their (i.e. server’s) private key to get the data.

  
## screen-stuff.md

      
              1 file
            
          
              16 forks
            
          
              1 comment
            
          
              19 stars
            
          
                gesellix
                / screen-stuff.md
            
            
              Created
              May 1, 2016 22:39
            
              
                screen and Docker for Mac
              
          
    screen ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty


screen -AmdS docker ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty
screen -r docker
# enter, then disconnect with Ctrl-a d
screen -S docker -p 0 -X stuff $(printf root\\r\\n)
screen -r docker


## prod-rds-snap-restore-to-dev-temp.sh
#!/bin/bash

# set up some variables

NOW_DATE=$(date '+%Y-%m-%d-%H-%M')
RESTORE_FROM_INSTANCE_ID=<source name>
TARGET_INSTANCE_ID=<target name>
TARGET_INSTANCE_CLASS=db.m4.large
VPC_ID=<vpc subnet id>
NEW_MASTER_PASS=<root password>

## create_cluster.sh
#!/usr/bin/env bash
#
# Purpose: Create a Swarm Mode cluster with a single master and a configurable
# number of workers.
# This script is a mirror of the following gist, which is used to
# populate a Medium story. Unfortunately, there's no way to synchronize all
# three
#
# Medium: https://medium.com/contino-io/docker-kata-005-ac8429082f6c
# Gist: https://gist.github.com/anonymuse/502e7bf5c7b67bb95a4250cdccbc5125

## changes.sh
#!/usr/bin/env bash

set -o errexit
set -o nounset
set -o pipefail

# org/repo (e.g. karlkfi/probe)
REPO=$1
# range (e.g. 1.8.4..1.8.5)
RANGE=$2
	#!/bin/bash

	# An set of disks to ignore from partitioning and formatting
	BLACKLIST="/dev/sda\|/dev/sdb"
	# Base directory to hold the data* files
	DATA_BASE="/media"

	usage() {
	echo "Usage: $(basename $0) <new disk>"
	}
	#!/bin/bash

	# set up some variables

	NOW_DATE=$(date '+%Y-%m-%d-%H-%M')
	RESTORE_FROM_INSTANCE_ID=<source name>
	TARGET_INSTANCE_ID=<target name>
	TARGET_INSTANCE_CLASS=db.m4.large
	VPC_ID=<vpc subnet id>
	NEW_MASTER_PASS=<root password>
	#!/usr/bin/env bash
	#
	# Purpose: Create a Swarm Mode cluster with a single master and a configurable
	# number of workers.
	# This script is a mirror of the following gist, which is used to
	# populate a Medium story. Unfortunately, there's no way to synchronize all
	# three
	#
	# Medium: https://medium.com/contino-io/docker-kata-005-ac8429082f6c
	# Gist: https://gist.github.com/anonymuse/502e7bf5c7b67bb95a4250cdccbc5125
	#!/usr/bin/env bash

	set -o errexit
	set -o nounset
	set -o pipefail

	# org/repo (e.g. karlkfi/probe)
	REPO=$1
	# range (e.g. 1.8.4..1.8.5)
	RANGE=$2