Steve Coffman StevenACoffman

GPG and GIT and SSH ... OH MY!

Assuming you are on a mac and set up your SSH key as described in detail below:

ssh-keygen -o -a 100 -t ed25519 -f ~/.ssh/id_ed25519 -C [email protected] -N ''

Then you won't be prompted for a passphrase. However, if you did have a passphrase:

ssh-keygen -o -a 100 -t ed25519 -f ~/.ssh/id_ed25519 -C [email protected] -N 'Really do not use this passphrase'

Then you will be prompted to type your passphrase every time you interact with git remote (pull, push, fetch, etc.) This is intolerable.

Why invest in golang:

Example of successful projects: docker, kubernetes, docker, kubernetes, influxdb, etcd, syncthing?
Fast: benchmark game, TechEmpower
Good for the planet - Low Energy Usage
Concurrency is a Joy in this language. Moore's law.
Popular Enough for Rich Ecosystem
- IEEE Spectrum 2018 - Go 9th
- IEEE Spectrum 2019 - Go 10th

StackOverflow 2019 Developer Survey - Go 13th

Kafka HPA: https://medium.com/google-cloud/kubernetes-hpa-autoscaling-with-kafka-metrics-88a671497f07

Monitoring

Some thoughts on monitoring.

Source Documents:

From this stackoverflow answer:

@Ainar-G suggests several great patterns to separate tests.

[This set of Go practices from SoundCloud][1] recommends using build tags ([described in the "Build Constraints" section of the build package][2]) to select which tests to run:

Write an integration_test.go, and give it a build tag of integration. Define (global) flags for things like service addresses and connect strings, and use them in your tests.

// +build integration

>

Create-react-app

Create React apps with no build configuration.

Thanks to create-react-app. It's saves a lot of my time. I remember several months ago I had to setup a lot just for a react app, webpack, babel, test environment and so on... Fortunately, everything becomes easy now. Though you have many choices of start boiler plate, you worth trying this.

React router

If you are build a SPA with react, you probably use react-router.

	ssh-keygen -o -a 100 -t ed25519 -f ~/.ssh/id_ed25519 -C [email protected] -N ''

	# -o : Save the private-key using the new OpenSSH format rather than the PEM format. Actually, this option is implied when you specify the key type as ed25519.
	# -a: It’s the numbers of KDF (Key Derivation Function) rounds. Higher numbers result in slower passphrase verification, increasing the resistance to brute-force password cracking should the private-key be stolen.
	# -t: Specifies the type of key to create, in our case the Ed25519.
	# -f: Specify the filename of the generated key file. If you want it to be discovered automatically by the SSH agent, it must be stored in the default `.ssh` directory within your home directory.
	# -C: An option to specify a comment. It’s purely informational and can be anything. But it’s usually filled with <login>@<hostname> who generated the key.
	# -N: Provides the new passphrase.
	eval "$(ssh-agent -s)"
	ssh-add -K ~/.ssh/id_ed25519

	///usr/bin/env go run "$0" "$@" ; exit "$?"
	package main

	import (
	"fmt"
	"gopkg.in/src-d/go-git.v4"
	"gopkg.in/src-d/go-git.v4/config"
	"gopkg.in/src-d/go-git.v4/plumbing"
	"gopkg.in/src-d/go-git.v4/plumbing/format/gitignore"
	"io/ioutil"

	///usr/bin/env go run "$0" "$@" ; exit "$?"
	package main

	import (
	"fmt"
	"os"

	"gopkg.in/src-d/go-git.v4"
	"gopkg.in/src-d/go-git.v4/plumbing"
	)

	FROM alpine:3.8 AS builder

	WORKDIR /opt
	ARG JDK_TAR=openjdk-11+28_linux-x64-musl_bin.tar.gz
	ARG JDK_DOWNLOAD_PREFIX=https://download.java.net/java/early_access/alpine/28/binaries

	RUN wget -q "$JDK_DOWNLOAD_PREFIX/$JDK_TAR" && \
	wget -q "$JDK_DOWNLOAD_PREFIX/$JDK_TAR.sha256"

	RUN cat $JDK_TAR.sha256 \| xargs -I{} echo "{} $JDK_TAR" \| sha256sum -c - && \