ldez

Gmail and GitHub

How to filter emails from GitHub in Gmail and flag them with labels.

The labels in this document are just examples.

Pull Request

Filter	Label

fertapric

$ ecs-run
Run a Docker container with the same configuration as an ECS service.

It uses the same image and environment variables of the ECS task definition.

Supported AWS CLI environment variables:
  - AWS_ACCESS_KEY_ID: AWS access key.
  - AWS_SECRET_ACCESS_KEY: AWS secret key.
  - AWS_SESSION_TOKEN: session token.
  - AWS_DEFAULT_REGION: AWS region.

fertapric

#!/bin/sh

print_help() {
  echo "Extract environment variables from an ECS service."
  echo
  echo "Usage: $0 [OPTIONS] SERVICE"
  echo
  echo "Options:"
  echo "    -h, --help      Print usage"
}

fertapric

Project at https://github.com/fertapric/files

SamSaffron

Tips for optimizing performance of the Discourse gigantic test suite

Change memory allocator

default:            9:37
tcmalloc:           8:32
lockless:           8:19
jemalloc 3.6.0: 7:45

fxn

Problem-Solving Games

My daughter and I love playing problem-solving/adventure games together. Here's a record of them.

1. Uncharted: The Lost Legacy
2. tint.
3. LEGO® Builder's Journey
4. Shadow of the Tomb Raider
5. Uncharted 4: A Thief's End
6. Grim Fandango Remastered

christos

Finding a Ruby memory leak using a time analysis

When developing a program in Ruby, you may sometimes encounter a memory leak. For a while now, Ruby has a facility to gather information about what objects are laying around: ObjectSpace.

There are several approaches one can take to debug a leak. This discusses a time-based approach, where a full memory dump is generated every, say, 5 minutes, during a time that the memory leak is showing up. Afterwards, one can look at all the objects, and find out which ones are staying around, causing the

wvengen

Finding a Ruby memory leak using a time analysis

When developing a program in Ruby, you may sometimes encounter a memory leak. For a while now, Ruby has a facility to gather information about what objects are laying around: ObjectSpace.

There are several approaches one can take to debug a leak. This discusses a time-based approach, where a full memory dump is generated every, say, 5 minutes, during a time that the memory leak is showing up. Afterwards, one can look at all the objects, and find out which ones are staying around, causing the

kamipo

default: &default
  adapter: mysql2
  encoding: utf8mb4
  username: root
  password:
  host: localhost
  variables:
    sql_mode: TRADITIONAL,NO_AUTO_VALUE_ON_ZERO,ONLY_FULL_GROUP_BY

development:

chrismdp

# You don't need Fog in Ruby or some other library to upload to S3 -- shell works perfectly fine
# This is how I upload my new Sol Trader builds (http://soltrader.net)
# Based on a modified script from here: http://tmont.com/blargh/2014/1/uploading-to-s3-in-bash

S3KEY="my aws key"
S3SECRET="my aws secret" # pass these in

function putS3
{
  path=$1