Add this little snippet to your ~/.gitconfig and it amps up your git pull by means of git up
pull --rebase - gets rid of unnecessary merge commits. If you don't know what rebase does, this is probably safe for you. If you know what rebase does, you should know where this will not be safe for you.Scott Chacon and Ryan Tomayko basically figured out how to do this and I am stealing all of the credit.
| net: require "net" | |
| sys: require "sys" | |
| LISTEN_PORT: 10000 | |
| SERVER_ADDRESS: '127.0.0.1' | |
| AVAILABLE_PORTS: [10001, 10002, 10003, 10004, 10005, 10006] | |
| CONNECTION_COUNTER: 0 | |
| reservePort: (callback) -> | |
| if AVAILABLE_PORTS.length > 0 |
| # Do something like: puts "ROCK".blink.bright.cyan | |
| class String | |
| def red | |
| "\e[31m#{self}\e[0m" | |
| end | |
| def blue | |
| "\e[34m#{self}\e[0m" | |
| end |
| # https://www.varnish-cache.org/docs/2.1/tutorial/vcl.html | |
| # https://www.varnish-cache.org/trac/wiki/VCLExamples | |
| # Summary | |
| # 1. Varnish will poll the backend at /health_check to make sure it is | |
| # healthy. If the backend goes down, varnish will server stale content | |
| # from the cache for up to 1 hour. | |
| # 2. Varnish will pass X-Forwarded-For headers through to the backend | |
| # 3. Varnish will remove cookies from urls that match static content file | |
| # extensions (jpg, gif, ...) |
| namespace :image_compression do | |
| desc 'Optimize images with pngcrush and jpegoptim' | |
| task :process do | |
| # Check for pngcrush | |
| if (!`which pngcrush`.empty? rescue false) # rescue on environments without `which` (windows) | |
| # Crush all .png files | |
| run "find #{shared_path}/assets/ -type f -name '*.png' -print0 | xargs -0 pngcrush -q -e .crushed" |
| sudo apt-get install libssl-dev | |
| sudo gem install fpm | |
| wget --timestamp ftp://ftp.ruby-lang.org//pub/ruby/1.9/ruby-1.9.3-p0.tar.gz | |
| tar -zxvf ruby-1.9.3-p0.tar.gz | |
| cd ruby-1.9.3-p0 | |
| time (./configure --prefix=/usr && make && make install DESTDIR=/tmp/installdir) | |
| fpm -s dir -t deb -n ruby -v 1.9.3-p0 -C /tmp/installdir \ | |
| -p ruby-VERSION_ARCH.deb -d "libstdc++6 (>= 4.4.3)" \ |
| i386 : iPhone Simulator | |
| x86_64 : iPhone Simulator | |
| arm64 : iPhone Simulator | |
| iPhone1,1 : iPhone | |
| iPhone1,2 : iPhone 3G | |
| iPhone2,1 : iPhone 3GS | |
| iPhone3,1 : iPhone 4 | |
| iPhone3,2 : iPhone 4 GSM Rev A | |
| iPhone3,3 : iPhone 4 CDMA | |
| iPhone4,1 : iPhone 4S |
Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = [email protected]:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
State machines are everywhere in interactive systems, but they're rarely defined clearly and explicitly. Given some big blob of code including implicit state machines, which transitions are possible and under what conditions? What effects take place on what transitions?
There are existing design patterns for state machines, but all the patterns I've seen complect side effects with the structure of the state machine itself. Instances of these patterns are difficult to test without mocking, and they end up with more dependencies. Worse, the classic patterns compose poorly: hierarchical state machines are typically not straightforward extensions. The functional programming world has solutions, but they don't transpose neatly enough to be broadly usable in mainstream languages.
Here I present a composable pattern for pure state machiness with effects,