| #!/bin/bash | |
| set -exo pipefail | |
| BUILD_ENV=$1 | |
| if [ `uname` == 'Darwin' ]; then | |
| OSX=1 | |
| JSCOMPRESSOR="yuicompressor --type js" | |
| else | |
| OSX= |
| require 'socket' | |
| NOT_FOUND = "HTTP/1.1 404 Not Found\nContent-Length: 9\n\nNot Found" | |
| OK = "HTTP/1.1 200 OK\n" | |
| socket = Socket.new(:INET, :STREAM) | |
| sockaddr = Socket.sockaddr_in(11080, '127.0.0.1') | |
| socket.bind(sockaddr) | |
| socket.listen(5) |
| #!/usr/bin/ruby | |
| # Make sure you have these gems installed | |
| require 'rubygems' | |
| require 'thread' | |
| require 'csv' | |
| require 'twitter' | |
| require 'marky_markov' | |
| # Create a new Twitter account that you'd like to have your auto-tweets posted to |
| Programming Elixer | |
| http://pragprog.com/book/elixir/programming-elixir | |
| Programming Clojure | |
| http://pragprog.com/book/shcloj2/programming-clojure | |
| Web Development with Clojure | |
| http://pragprog.com/book/dswdcloj/web-development-with-clojure | |
| Purely Functional Data Structures |
The following is an explanation of Ruby blocks and yield by another Bloc mentor (Adam Louis) who was trying to explain it to one of his students.
On my very first day programming, if someone asked me for "the sum of the numbers from 1 to 10", I'd have written:
puts 1 + 2 + 3 + 4 + 5 + 6 + 7 + 8 + 9 + 10
Easy enough.
| Chrome | |
| Alfred | |
| Dropbox | |
| 1Password | |
| Sizeup | |
| Coconut Battery | |
| Dash | |
| XCode | |
| Caffeine |
Build your dotfiles (shell, Vim config) from multiple sources with fresh.
Both of our dotfiles are built using fresh. We source Vim and other config from each other:
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
| # | |
| # Working with branches | |
| # | |
| # Get the current branch name (not so useful in itself, but used in | |
| # other aliases) | |
| branch-name = "!git rev-parse --abbrev-ref HEAD" | |
| # Push the current branch to the remote "origin", and set it to track | |
| # the upstream branch | |
| publish = "!git push -u origin $(git branch-name)" |