Ruby 2.0 by example
benhoskin.gs2 pointsby ben_h0 comments
bash -c "`curl -L babushka.me/up`" # If you're on a Mac
bash -c "`wget -O - babushka.me/up`" # If you're on Ubuntu
Some good examples to start with: babushka rubygems # Installs, updates, or adds gem sources as required for your system
babushka homebrew # Sets you up for sudoless `brew install`s
babushka Cucumber.tmbundle # Clones the latest, installing / restarting TextMate as required
babushka Chromium.app # Pulls the latest Chromium nightly to /Applications
If you want to see what will happen without making any changes, use `--dry-run`: babushka Transmit.app --dry-run
If you're on a Mac, you can follow along in TextMate too using `--track-blocks` — babushka points out each piece of each dep as it runs them. (This also works with `--dry-run`, so you can inspect the code a tree of deps would run.) mate /usr/local/babushka
babushka 'Ruby on Rails.tmbundle' --track-blocks
Any questions, get in touch with @babushka_app on Twitter, #babushka on Freenode, or email [email protected]. bash -c "`curl -L babushka.me/up`"
And then running this babushka homebrew
Will get you all set up with homebrew. But what it does is achieve the end goal of having homebrew set up—which might mean doing nothing, or cloning a git repo, or possibly just doing a `git reset --hard` to drop a binary in place. It depends on the system. The upshot though, is that if you're working on some other problem and a new colleague needs homebrew, you can run one command and you're done, instead of getting sidetracked for 15 minutes. vim_plugin "vim-cucumber" do
source "git://github.com/tpope/vim-cucumber.git"
end
You can run that dep with a single command, even if you've never used Josh's dep source before: babushka nullobject/vim-cucumber
And so on, to configure anything and everything you like. It's already doing this job, which I'm really excited about. http://twitter.com/harvinius/status/13116470017
(We have a separate cookie that is present for signed-in users, so the fronted knows whether it should fire the annotation request.)
The result is that we can serve a sudden influx of unauthenticated users (e.g. from Google News or StumbleUpon) from nginx alone, which gives us massive scale from very little hardware. It's likely that the network is actually the bottleneck in this case, and not nginx.