liquid1982

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

liquid1982

tmux cheatsheet

As configured in my dotfiles.

start new:

tmux

start new with session name:

liquid1982

gem 'devise'

gem 'omniauth'
gem 'omniauth-github'
gem "omniauth-twitter"
gem "omniauth-facebook"
gem "omniauth-google-oauth2"

liquid1982

#!/sbin/runscript
# GitLab init script for Gentoo Linux
# see https://github.com/gitlabhq/gitlabhq/blob/master/doc/installation.md

GITLAB_BASE=/home/gitlab/gitlab
GITLAB_USER=gitlab

depend() {
	need net mysql redis
}

liquid1982

#! /bin/bash

### BEGIN INIT INFO
# Provides:          unicorn
# Required-Start:    $local_fs $remote_fs $network $syslog
# Required-Stop:     $local_fs $remote_fs $network $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: starts the unicorn web server
# Description:       starts unicorn

liquid1982

include Tire::Model::Search
include Tire::Model::Callbacks
  
settings :analysis => {
            :filter => {
              :ngram_filter  => {
                :type => 'edgeNGram',
                :min_gram => 1,
                :max_gram => 10,
                :side => 'front'

liquid1982

# Example code and benchmark harness for http://blog.gregspurrier.com/articles/arbitrary-reordering-of-ruby-arrays

require 'rubygems'
require 'rspec'

module Enumerable
  def reorder_by1(order, &key_proc)
    order.map do |x|
      find {|obj| key_proc.call(obj) == x}
    end