Raynos

ES6 what can be shimmed and what not.

Currently only lists things that can be shimmed or are experimentally implemented

Note that for any kind of decent ES6 support we need an ES6 transpiler. A few projects are attempting this [Reference SO question][3]

• [traceur][4]
• [Caja][5]
• [ES transpiler][6]

henrik

tmux cheatsheet

As configured in my dotfiles.

start new:

tmux

start new with session name:

1stvamp

#!/bin/bash
mkdir /tmp/curl-ca-bundle
cd /tmp/curl-ca-bundle
wget http://curl.haxx.se/download/curl-7.22.0.tar.bz2
tar xzf curl-7.22.0.tar.bz2
cd curl-7.22.0/lib/
./mk-ca-bundle.pl
if [ ! -d /usr/share/curl/ ]; then
	sudo mkdir -p /usr/share/curl/
else

andreyvit

tmux cheat sheet

(C-x means ctrl+x, M-x means alt+x)

Prefix key

The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:

remap prefix to Control + a

MohamedAlaa

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

follmann

Manual and upstart config for AeroFS (aerofs-cli) on Ubuntu 12.04.1 LTS:

# link standard upstart script 
cd /etc/init.d 
sudo ln -s /lib/init/upstart-job aerofs-cli

# create upstart config for aerofs-cli 
sudo nano /etc/init/aerofs-cli.conf 
(replace andreas with your desired runtime user) 
---- 

flomotlik

      'CI' => true,
      'CI_BUILD_NUMBER' => id,
      'CI_BUILD_URL' => project_build_url(project, self),
      'CI_PULL_REQUEST' => false,
      'CI_BRANCH' => branch,
      'CI_COMMIT_ID' => commit_id,
      'CI_COMMITTER_NAME' => name,
      'CI_COMMITTER_EMAIL' => email,
      'CI_COMMITTER_USERNAME' => github_username,
      'CI_MESSAGE' => message,

kates

ag "sometext" --nogroup | awk '{print substr($1,1,index($1,":")-1);}' | xargs -I {} sed -i .bak -e 's/sometext/anothertext/g' {}

drogus

require 'bundler/setup'

require 'active_record'

include ActiveRecord::Tasks

db_dir = File.expand_path('../db', __FILE__)
config_dir = File.expand_path('../config', __FILE__)

DatabaseTasks.env = ENV['ENV'] || 'development'

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying