Sherif Abdalla ZeroDeth

THIS WAS ORIGINALLY POSTED ON MY TUMBLR ON FEB 25, 2011. I forgot I had a Tumblr account. I recently logged in (in light of the acquisition by Automattic), found some old posts, and I'm republishing them exactly as they were with zero modifications.

CloudFormation: The Big Picture

Amazon announced CloudFormation to the public yesterday, and while the general opinion I could glean from various sources shows that people are excited about this new technology, many are still unsure what it is and how it fits into their current cloud workflow. I feel as though I have a firm grasp on CloudFormation and will attempt to answer some questions here.

Note: I'm definitely not a representative of Amazon in any way, and anything here is simply my educated opinion on the matter.

Source: https://gitlab.com/gitlab-org/gitlab-runner/issues/1583#note_93170156

OK, I've experimented a lot getting this going with the docker+machine executor (specifically with the amazonec2 driver, which I suspect is quite common for people looking at this thread!), it may also be helpful to others when debugging what's going on for them.

docker+machine is interesting because it has several relevant contexts (i.e. a file system and environment variables), which I shall refer to as:

"runner": what is running the gitlab-runner binary - in my case this is an ECS-managed docker container for the gitlab/gitlab-runner image on docker hub, but it could the systemd service configuration if you're running directly on the machine.
"job host": the docker-machine created machine (e.g. EC2 instance) that runs the docker daemon
"job container": the docker container for the image specified in the project .gitlab-ci.yaml (or the default in config.toml)

Comparison of ZSH frameworks and plugin managers

Changelog

update 1: add a FAQ section
update 2: benchmark chart and feature comparison table
update 3:
- improve the table with missing features for antigen
- new zplg times result

TLDR

Import Keybase PGP to GPG

After installing the keybase command-line tool onto a new / fresh computer, you may want to import your PGP key to the local keyring so that you may use the keys with GPG.

Import your PUBLIC PGP key:

keybase pgp export|gpg --import -

	apiVersion: extensions/v1beta1
	kind: Ingress
	metadata:
	namespace: argocd
	name: argocd-ingress
	annotations:
	kubernetes.io/ingress.class: alb
	alb.ingress.kubernetes.io/scheme: internet-facing
	alb.ingress.kubernetes.io/listen-ports: '[{"HTTP":80,"HTTPS": 443}]'
	alb.ingress.kubernetes.io/certificate-arn: {{ your-acm-arn }}

	# get api token with proper perms, ensure full "repos" for private repo access.

	$ export auth="Authorization: token 123345465hfghfghfghgfhgfhfg"
	$ export org="your_org"

	# get the last page in the Link header. github API limits per_page to 100. Anything over this will require pagination.
	$ curl -I -H "$auth" https://api.github.com/orgs/$org/repos

	# go over all pages. Put this in a script, and save it.
	#!/bin/bash

	#!/bin/bash

	# Get directory of script
	DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"

	if [[ $# -ne 1 ]]
	then
	echo "ERROR: This script expects the namespace name to be given as an argument"
	echo "e.g. ./ecr-cred-updater.sh my-namespace"
	exit 1

	version: 0.2

	env:
	parameter-store:
	build_ssh_key: "build_ssh_key"

	phases:
	install:
	commands:
	- mkdir -p ~/.ssh

	# Reference: https://www.exclamationlabs.com/blog/continuous-deployment-to-npm-using-gitlab-ci/

	# GitLab uses docker in the background, so we need to specify the
	# image versions. This is useful because we're freely to use
	# multiple node versions to work with it. They come from the docker
	# repo.
	# Uses NodeJS V 9.4.0
	image: node:9.4.0

	# And to cache them as well.

	version: '2'
	services:
	plex:
	image: linuxserver/plex
	container_name: plex
	volumes:
	- /path/to/plex/config:/config
	- /path/to/plex/Movies:/data/movies
	- /path/to/plex/Shows:/data/tvshows
	- /path/to/plex/transcode:/data/transcode