• Sat Jan 21
  • Desktop January 2012.

  • Thu Jan 19
  • Wed Jan 18
  • This looks super smart. Clean unobtrusive wall mountable desk.

    (via swiss-miss)

  • Fantastic capture of the cruise ship disaster off the coast of Giglio, Italy

  • Tue Jan 17
    # rails < 3.1
    new_record = old_record.clone
    
    #rails >= 3.1
    new_record = old_record.dup
  • If you’re running a Rails app locally on pow and get an ‘unknown process error’ , I’ve found the following to be quite a reliable fix:

    1. Try restarting pow

    $ touch tmp/restart.txt

    If that doesn’t work it’s likely something is broken in your code. Sometimes pow doesn’t catch basic syntax errors.

    2. Run the native Rails server

    $ rails s

    This should output the errors (if any) from your code.

  • A quick reference for setting up a new rvm gemset ready for Rails 3.1.

    Follow along, using Terminal or iTerm.

    1. Install Ruby 1.9.3

    rvm install 1.9.3

    If you want, make this rvm the default.

    rvm use 1.9.3 --default

    2. Create your new Rails 3.1.3 gemset.

    rvm gemset create rails313

    3. Select the gemset.

    rvm use ruby-1.9.3-p0@rails313 --default

    4. Install Rails.

    gem install rails

    This will install rails, bound to the gemset we just created.

    You can also optionally create an .rvmc file in various projects to ensure they run on the correct gemset. This is done by running the following in your individual project directory:

    rvm --rvmrc --create use ruby-1.9.3-p0@rails313
  • Mon Jan 16
  • Spoooogett.

  • NYE.

Page 1 of 512345