Aleksandr Kostyrev kostyrev

Extracting Emoji From Slack!

Slack doesn't provide an easy way to extract custom emoji from a team. (Especially teams with thousands of custom emoji) This Gist walks you through a relatively simple approach to get your emoji out.

If you're an admin of your own team, you can get the list of emoji directly using this API: https://api.slack.com/methods/emoji.list. Once you have it, skip to Step 3

HOWEVER! This gist is intended for people who don't have admin access, nor access tokens for using that list.

Follow along...

Git DMZ Flow

I've been asked a few times over the last few months to put together a full write-up of the Git workflow we use at RichRelevance (and at Precog before), since I have referenced it in passing quite a few times in tweets and in person. The workflow is appreciably different from GitFlow and its derivatives, and thus it brings with it a different set of tradeoffs and optimizations. To that end, it would probably be helpful to go over exactly what workflow benefits I find to be beneficial or even necessary.

Two developers working on independent features must never be blocked by each other
- No code freeze! Ever! For any reason!
A developer must be able to base derivative work on another developer's work, without waiting for any third party
Two developers working on inter-dependent features (or even the same feature) must be able to do so without interference from (or interfering with) any other parties
Developers must be able to work on multiple features simultaneously, or at lea

An introduction to curl using GitHub's API.

Basics

Makes a basic GET request to the specifed URI

curl https://api.github.com/users/caspyin

Includes HTTP-Header information in the output

Internet Scale Services Checklist

A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."

http://mvdirona.com/jrh/talksandpapers/jamesrh_lisa.pdf

Basic tenets

Does the design expect failures to happen regularly and handle them gracefully?
Have we kept things as simple as possible?

Nginx FastCGI response buffer sizes

By default when Nginx starts receiving a response from a FastCGI backend (such as PHP-FPM) it will buffer the response in memory before delivering it to the client. Any response larger than the set buffer size is saved to a temporary file on disk.

This process is outlined at the Nginx ngx_http_fastcgi_module page manual page.

Introduction
Determine actual FastCGI response sizes
Setting the buffer size
Verifying results

	#!/bin/sh

	# Use AWS CLI to get the most recent version of an AMI that
	# matches certain criteria. Has obvious uses. Made possible via
	# --query, --output text, and the fact that RFC3339 datetime
	# fields are easily sortable.

	export AWS_DEFAULT_REGION=us-east-1

	aws ec2 describe-images \

	# Fetch
	git clone https://github.com/username/reponame reponame
	for b in `git branch -r \| grep -v -- '->'`; do git branch --track ${b##origin/} $b; done

	# Analyze
	curl https://bootstrap.pypa.io/get-pip.py > get-pip.py && sudo python get-pip.py && rm get-pip.py
	sudo pip install git-fat
	git fat -a find 1000000

	git ls-tree -r -t -l --full-name HEAD \| sort -n -k 4

	#!/bin/bash

	instance_profile=`curl http://169.254.169.254/latest/meta-data/iam/security-credentials/`
	aws_access_key_id=`curl http://169.254.169.254/latest/meta-data/iam/security-credentials/${instance_profile} \| grep AccessKeyId \| cut -d':' -f2 \| sed 's/[^0-9A-Z]*//g'`
	aws_secret_access_key=`curl http://169.254.169.254/latest/meta-data/iam/security-credentials/${instance_profile} \| grep SecretAccessKey \| cut -d':' -f2 \| sed 's/[^0-9A-Za-z/+=]*//g'`
	token=`curl -s http://169.254.169.254/latest/meta-data/iam/security-credentials/${instance_profile} \| sed -n '/Token/{p;}' \| cut -f4 -d'"'`

	file="somefile.deb"
	bucket="some-bucket-of-mine"
	date="`date +'%a, %d %b %Y %H:%M:%S %z'`"

	# Edit ~/.bash_profile

	export GOPATH=/Users/$USER/go
	export PATH=$GOPATH/bin:$PATH

	# Reload profile : source ~/.bash_profile

	#!/bin/bash
	#
	# Assume the given role, and print out a set of environment variables
	# for use with aws cli.
	#
	# To use:
	#
	# $ eval $(./iam-assume-role.sh)
	#