Brandon Sturgeon brandonsturgeon

Intro

Do you rebase often? Ever forget to --force on your subsequent push? This annoyance and impatience could tempt you into making a new alias, like:

git config --global alias.pushf 'push --force'

Yes, this will save you time. But will it save you headache? Maybe not.

--force is a destructive command by definition. It changes history.

Shaman BiS List

Restoration Shaman

Slot	Name	Source
Head	Sanctified Frost Witch's Headpiece	Vendor
Neck	Blood Queen's Crimson Choker	Blood Queen Lana'thel 25HC
Shoulders	Sanctified Frost Witch's Spaulders	Vendor
Back	Cloak of Burning Dusk	Halion 25HC

Creating Releases with PGP Signatures

Aleksa Sarai

Creating a release of a free software project with PGP signatures is quite simple, especially if you have everything set up already. This guide uses GnuPG, but it should be roughly applicable to OpenPGP or other implementations. For completeness, I've included a (very) short introduction to how to create a PGP key and how PGP works.

Introduction

Use curl to get the JSON response for the latest release
Use grep to find the line containing file URL
Use cut and tr to extract the URL
Use wget to download it

curl -s https://api.github.com/repos/jgm/pandoc/releases/latest \
| grep "browser_download_url.*deb" \
| cut -d : -f 2,3 \
| tr -d \" \

Every so often I have to restore my gpg keys and I'm never sure how best to do it. So, I've spent some time playing around with the various ways to export/import (backup/restore) keys.

Method 1

Backup the public and secret keyrings and trust database

cp ~/.gnupg/pubring.gpg /path/to/backups/
cp ~/.gnupg/secring.gpg /path/to/backups/
cp ~/.gnupg/trustdb.gpg /path/to/backups/

or, instead of backing up trustdb...

The Ultimate Git Alias Setup

If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.

Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.

The simplest way to add an alias for a specific git command is to use a standard bash alias.

# .bashrc

	local RED = Color(255, 0, 0, 235)
	local BLUE = Color(0, 0, 255, 235)
	local WHITE = Color(255, 255, 255, 230)

	local beamColor = RED

	local beams = {}
	local claws = ents.FindByClass("npc_clawscanner")

	local Sounds = {

	// GET /api/v1/cmss (better name needed)
	{ "cmss": [
	{"client_name": "Cody's Adventure Time",
	"site_url": "https://g5-cms-iwmpeigo-cody-test-cms.herokuapp.com"
	},
	{"client_name": "Another Client",
	"site_url": "https://g5-cms-iwmpeigo-another-client.herokuapp.com"
	},
	]}

	// see for screenshot:
	// https://twitter.com/paul_irish/status/829090506084749312

	const http = require('http');

	function requestHandler(request, response) {
	const headers = {
	'Server-Timing': `
	sql-1;desc="MySQL lookup Server";dur=100,
	sql-2;dur=900;desc="MySQL shard Server #1",

	echo "Creating an SSH key for you..."
	ssh-keygen -t rsa

	echo "Please add this public key to Github \n"
	echo "https://github.com/account/ssh \n"
	read -p "Press [Enter] key after this..."

	echo "Installing xcode-stuff"
	xcode-select --install