the reality of using a "microframework"

001-Isolate

# what I put in an Isolate gem list, ok, so "gem install isolate" first...

gem "sinatra", "1.3.1"
gem "haml", "3.1.3"
gem "sass", "3.1.10"
gem "activerecord", "3.1.1"
gem "sqlite3", "1.3.4"
gem "sinatra-activerecord", "0.1.3"
gem "rack", "1.3.5"
gem "bacon", "1.1.0"
gem "autotest", "4.4.6"
gem "autotest-fsevent", "0.2.7"
gem "padrino-helpers", "0.10.5"

002-gems

# a couple of other gems to make things tolerable

gem install shotgun racksh

003-gem-list

# gem list ... i.e., what I ended up with (a total of 36 gems):

@ ruby-1.8.7@donate_this Mon Nov 14 18:15:23 rick@Yer-Moms-Computer-2
~/git/donate_this (work)(*)$ gem list

*** LOCAL GEMS ***

activemodel (3.1.1)
activerecord (3.1.1)
activesupport (3.1.1)
arel (2.2.1)
autotest (4.4.6)
autotest-fsevent (0.2.7)
bacon (1.1.0)
builder (3.0.0)
cgi_multipart_eof_fix (2.5.0)
daemons (1.1.4)
fastthread (1.0.7)
gem_plugin (0.2.3)
haml (3.1.3)
http_router (0.10.2)
i18n (0.6.0)
isolate (3.2.1)
multi_json (1.0.3)
padrino-core (0.10.5)
padrino-helpers (0.10.5)
rack (1.3.5)
rack-protection (1.1.4)
rack-test (0.6.1)
racksh (0.9.8)
rake (0.9.2)
rdoc (3.9.4)
sass (3.1.10)
shotgun (0.9)
sinatra (1.3.1)
sinatra-activerecord (0.1.3)
sqlite3 (1.3.4)
sys-uname (0.8.6)
thor (0.14.6)
tilt (1.3.3)
tzinfo (0.3.31)
url_mount (0.2.1)
ZenTest (4.6.2)