splam 0.1.0

data/lib/splam/rules/fuzz.rb

@@ -0,0 +1,20 @@
+class Splam::Rules::Fuzz < Splam::Rule
+  class << self
+    attr_accessor :bad_word_score
+  end
+  
+  self.bad_word_score       = 10
+
+  def run
+    patterns = [/^(\d[a-z])/, /(\d[a-z][A-Z]\w+)/, /(\b\w+\d\.txt)/, /(;\d+;)/ ]
+    matches = 0
+    patterns.each do |pattern|
+      results = @body.scan(pattern)
+      if results && results.size > 0
+        add_score((self.class.bad_word_score * results.size), "bad pattern match: '#{$1}'")
+      end
+      matches += results.size
+    end
+    add_score matches.size ** 4, "Aggregate number of bad patterns was #{matches}." if matches > 1
+  end
+end

data/lib/splam/rules/good_words.rb

@@ -0,0 +1,19 @@
+class Splam::Rules::GoodWords < Splam::Rule
+  
+  def run
+    good_words = [ /I\'having a problem/, ]
+    good_words |= %w( lighthouse activereload  warehouse install eclipse settings assigned user ticket tickets token api number query request)
+    good_words |= %w( browser feed firefox safari skitch vendor rails action_controller railties )
+    good_words |= %w( redirect login diff dreamhost setup subversion git  wildcard domain subdomain ssh database )
+    good_words |= %w( project billing tags description comment milestone saving happening feature mac implement report)
+    good_words |= %w( rss notification subscribe calendar chart note task gantt search service ownership application communicate )
+    good_words |= %w( pattern template web integer status xml activereload html state page)
+    good_words << "project management"
+    good_words << "/usr/local/lib" << "gems"
+
+    body = @body.downcase
+    good_words.each { |rule| 
+      add_score -5 * body.scan(rule).size, "relevant word match: #{rule}"
+    }
+  end
+end

data/lib/splam/rules/href.rb

@@ -0,0 +1,55 @@
+# This plugin checks for links in the text, and adds scores for having many links,
+# and 
+class Splam::Rules::Href < Splam::Rule
+  
+  def run
+    # add_score 3 * @body.scan("href=http").size, "Shitty html 'href=http'" # 3 points for shitty html
+    add_score 15 * @body.scan(/href\=\s*http/).size, "Shitty html 'href=http'" # 15 points for shitty html
+    add_score 15 * @body.scan(/href\="\s+http/).size, "Shitty html 'href=\" http'" # 15 points for shitty html
+    add_score 50 * @body.scan(/\A<a.*?<\/a>\Z/).size, "Single link post'"      # 50 points for shitty
+
+    link_count = @body.scan("http://").size
+    add_score 1 * link_count, "Matched 'http://'" # 1 point per link
+    add_score 50, "More than 10 links" if link_count > 10  # more than 10 links? spam.
+    add_score 100, "More than 20 links" if link_count > 20 # more than 20 links? definitely spam.
+    add_score 1000, "More than 50 links" if link_count > 50 # more than 20 links? definitely spam.
+    
+    # Modify these scores to weight certain problematic domains.
+    # You may need to modify these for your application
+    suspicious_top_level_domains = {
+      'ru' => 20,  # Russian? spammer.
+      'cn' => 20,  # Chinese? spammer.
+      'us' => 8,   # .us ? possibly spam
+      'it' => 5,
+      'tk' => 20,
+      'pl' => 8,
+      'info' => 20, 
+      'biz'  => 40 # no-one uses these for reals
+    }
+    suspicious_sites = {
+      'cnn' => 10, # Honestly, who links to CNN?
+      'bbc' => 10
+    }
+    
+    tokens = @body.split(" ")
+    if tokens[-1] =~ /^http:\/\//
+      add_score 10, "Text ends in a http token"
+      add_score 50, "Text ends in a http token and only has one token" if link_count == 1
+    end
+    
+    @body.scan(/http:\/\/(.*?)[\/\]?]/) do |match|
+      # $stderr.puts "checking #{match}"
+      if domain = match.to_s.split(".")
+        tld = domain[-1]
+
+        if found = suspicious_top_level_domains[tld]
+          add_score found, "Suspicious top-level domain: '#{tld}'"
+        end
+        
+        if found = suspicious_sites[domain[-2]]
+          add_score found, "Suspicious hostname: '#{domain[-2]}'"
+        end
+      end
+    end
+  end
+end

data/lib/splam/rules/html.rb

@@ -0,0 +1,12 @@
+class Splam::Rules::Html < Splam::Rule
+  
+  def run
+    # you get points for having lots of links
+    add_score @body.scan(/\<[abi]/).size, "Lots of <a> <b> or <i> links"
+    
+    # stupid fools!
+    add_score 5 * @body.scan(/<a[^>]*><b>/).size, "<b> inside an <a>"
+    
+    add_score(200, "Entire body is an HTML tag") if @body =~ /^[<][^>]*[>]$/
+  end
+end

data/lib/splam/rules/line_length.rb

@@ -0,0 +1,26 @@
+class Splam::Rules::LineLength < Splam::Rule
+  
+  def name
+    "Line length"
+  end
+  
+  # Penalize long line lengths.
+  def run
+    lines = @body.split("\n")
+    lines.each do |line|
+      next if line =~ /\A\s{4,}/ # ignore code blocks
+
+      multiplier = (lines.size == 1) ? 10 : 1 # one line? fail.
+        
+      
+      # 1 point for each 40 chars in a line.
+      hits = (line.size / 40) * multiplier
+      add_score hits, "lines over 40 chars"
+      
+      # 2 more points if line is longer than 80
+      hits = (line.size / 80) * 2 * multiplier
+      add_score hits, "lines over 80 chars"
+
+    end
+  end
+end

data/lib/splam/rules/punctuation.rb

@@ -0,0 +1,14 @@
+class Splam::Rules::Punctuation < Splam::Rule
+  
+  def run
+    punctuation = @body.scan(/[.,] /)
+    add_score 10, "Text has no punctuation" if punctuation.size == 0
+
+    @body.split(/[.,]/).each do |sentence|
+      words = sentence.split(" ")
+      # long sentence, add a point.
+      add_score 1, "Sentence has more than 10 words" if words.size > 10
+      add_score 10, "Sentence has more than 30 words" if words.size > 30
+    end
+  end
+end

data/lib/splam/rules/russian.rb

@@ -0,0 +1,15 @@
+class Splam::Rules::Russian < Splam::Rule
+
+  def run
+    banned_words =[ # various russian characters
+      "\320\241", "\320\220", "\320\234", "\320\257", "\320\233", "\320\243", 
+      "с", "м", "о", "т", "р", "е", "т", "ь", "п", "о", "р", "н", "о", "р", "л", "и", "к"
+      # unicode char
+#      "\320"
+    ]
+    banned_words.each do |word|
+      hits = (3 * @body.scan("#{word}").size) # 1 point for every banned word
+      add_score hits, "Suspicious character '#{word}'"
+    end
+  end
+end

data/lib/splam/rules/word_length.rb

@@ -0,0 +1,32 @@
+class Splam::Rules::WordLength < Splam::Rule
+
+  # Basic array functions
+  def sum(arr)
+    arr.inject  {|sum,x| sum + x }
+  end
+
+  def average(arr)
+    sum(arr) / arr.size
+  end
+  
+  def median(arr)
+    a2 = arr.sort
+    a2[arr.size / 2] unless arr.empty?
+  end
+  
+  def run
+    words = []
+    words = @body.split(/\s/).map do |word|
+      word.size
+    end
+    words.delete_if { |w| w =~ /^http\:\/\//}
+
+    # Only count word lengths over 10
+    if words.size > 5
+      add_score 20, "Average word length over 5"  if average(words) > 5
+      add_score 50, "Average word length over 10" if average(words) > 10
+      add_score 10, "Median word length over 5"   if median(words) > 5
+      add_score 50, "Median word length over 10"  if median(words) > 10
+    end
+  end
+end

data/splam.gemspec

@@ -0,0 +1,12 @@
+name = "splam"
+
+Gem::Specification.new name, "0.1.0" do |s|
+  s.summary = "Run any kind of code in parallel processes"
+  s.authors = ["ENTP"]
+  s.email = "ENTP@example.com"
+  s.homepage = "http://github.com/grosser/#{name}"
+  s.files = `git ls-files`.split("\n")
+  s.license = "MIT"
+  s.signing_key = File.expand_path("~/.ssh/gem-private_key.pem")
+  s.cert_chain = ["gem-public_cert.pem"]
+end

data/test/fixtures/comment/ham/api-1.txt

@@ -0,0 +1 @@
+"This":http://activereload.lighthouseapp.com/projects/44-lighthouse-users/tickets.xml?q=state%3Aopen&page=2 doesn't work for you?  Sending ?page=2 should work fine. It's basically an XML version of the html page.  Try it without the .xml extension, and it should match the xml feed.

data/test/fixtures/comment/ham/api-2.txt

@@ -0,0 +1,7 @@
+Rick -
+
+Thanks again.  I, after wrestling with a case of dyslexia, got it to work with you suggestion. I wasn't encoding the colon for some reason.  Idiot me.
+
+I'm probably going to put together a little 'dummies guide' for the API once I get done with this projects, because I think it would help others who might have had some similar initial glitches.
+
+THANKS for a great product!

data/test/fixtures/comment/ham/api-3.txt

@@ -0,0 +1,3 @@
+Rick, is there a way to get all data without making requests page-by-page.  If not, is there a way to get the total number of items?
+
+Thanks.

data/test/fixtures/comment/ham/api-4.txt

@@ -0,0 +1 @@
++1 on the no-pagination request.  Thanks!

data/test/fixtures/comment/ham/api-5.txt

@@ -0,0 +1,7 @@
+While no-pagination would be nice I can understand why it exists. If you have 100s of tickets then you're going to have an absolutely huge XML file to generate and load. The easy way to work through is:
+
+if (number of tickets on page == 30) {
+     get next page
+} else {
+     got all tickets
+}

data/test/fixtures/comment/ham/api.txt

@@ -0,0 +1,5 @@
+Hey guys.  So after a long night, I could finally get the API to do what I need to.  But I can't seem to access anything past the first 30 tickets.  
+
+http://xxx.lighthouseapp.com/projects/xxx/tickets.xml?q=state:open
+
+I've tried adding ?page=1 then 2 then 3, but I can't seem to get anything but the first original 30 tickets.  I know there are 65 tickets that match that request.  Any suggestions?

data/test/fixtures/comment/ham/api_bug.txt

@@ -0,0 +1,16 @@
+I get this error message when changing the milestone on a ticket and then saving it:
+
+    ActiveResource::ServerError (Failed with 500 Internal Server Error):
+    /usr/local/lib/ruby/gems/1.8/gems/activeresource-2.1.0/lib/active_resource/connection.rb:173:in `handle_response'
+    /usr/local/lib/ruby/gems/1.8/gems/activeresource-2.1.0/lib/active_resource/connection.rb:144:in `request'
+    /usr/local/lib/ruby/gems/1.8/gems/activeresource-2.1.0/lib/active_resource/connection.rb:121:in `put'
+    /usr/local/lib/ruby/gems/1.8/gems/activeresource-2.1.0/lib/active_resource/base.rb:929:in `update'
+    /usr/local/lib/ruby/gems/1.8/gems/activeresource-2.1.0/lib/active_resource/base.rb:779:in `save_without_validation'
+    /usr/local/lib/ruby/gems/1.8/gems/activeresource-2.1.0/lib/active_resource/validations.rb:262:in `save_without_tags'
+    /lib/lighthouse.rb:181:in `save'
+
+A few days ago this wasn't happening - and now it happens even through ./script/console
+
+Any thoughts or ideas?
+
+Thanks

data/test/fixtures/comment/ham/backtrace.txt

@@ -0,0 +1,79 @@
+Hey guys,
+
+Installed 1.1.1 and upon clicking the "Hooks" button, I get the following error:
+
+[code]Processing HooksController#index (for 192.168.1.85 at 2007-10-15 11:08:32) [GET]
+  Session ID: BAh7BiIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNo%0ASGFzaHsABjoKQHVzZWR7AA%3D%3D--fbec10b5ed11e70564577d7f46ee0f5f6a40f597
+  Parameters: {"action"=>"index", "controller"=>"hooks"}
+Rendering template within layouts/application
+Rendering hooks/index
+
+[code]ActionView::TemplateError (undefined method `repo' for nil:NilClass) on line #2 of app/views/hooks/_hook.html.erb:
+1: <li id="hook-<%= hook.plugin_name %>" class="listitem">
+2:   <% remote_sheet_form_for :hook, hook.properties, :url => hooks_path(:name => hook.plugin_name), 
+3:          :trigger => "hooknew-#{hook.plugin_name}", :html => {:id => "hooksheet-#{hook.plugin_name}", :style => 'display:none'} do |s| %>
+4:     <h2>Add <%= hook.title %> Instance</h2>
+5:     <%= s.text_field "Label:", :label %>
+
+    lib/warehouse/hooks/base.rb:12:in `initialize'
+    lib/warehouse/hooks/base.rb:17:in `new'
+    lib/warehouse/hooks/base.rb:17:in `properties'
+    app/views/hooks/_hook.html.erb:2:in `_run_erb_47app47views47hooks47_hook46html46erb'
+    vendor/rails/actionpack/lib/action_view/base.rb:377:in `send'
+    vendor/rails/actionpack/lib/action_view/base.rb:377:in `compile_and_render_template'
+    vendor/rails/actionpack/lib/action_view/base.rb:353:in `render_template'
+    vendor/rails/actionpack/lib/action_view/base.rb:303:in `render_file'
+    vendor/rails/actionpack/lib/action_view/base.rb:318:in `render'
+    vendor/rails/actionpack/lib/action_view/partials.rb:117:in `render_partial'
+    vendor/rails/actionpack/lib/action_controller/benchmarking.rb:30:in `benchmark'
+    vendor/rails/actionpack/lib/action_view/partials.rb:116:in `render_partial'
+    vendor/rails/actionpack/lib/action_view/partials.rb:143:in `render_partial_collection'
+    vendor/plugins/expiring_attr_reader/lib/expiring_attr_reader.rb:32:in `each_with_index'
+    vendor/rails/actionpack/lib/action_view/partials.rb:141:in `each'
+    vendor/rails/actionpack/lib/action_view/partials.rb:141:in `each_with_index'
+    vendor/rails/actionpack/lib/action_view/partials.rb:141:in `render_partial_collection'
+    vendor/rails/actionpack/lib/action_view/base.rb:337:in `render'
+    app/views/hooks/index.html.erb:4:in `_run_erb_47app47views47hooks47index46html46erb'
+    vendor/rails/actionpack/lib/action_view/base.rb:377:in `send'
+    vendor/rails/actionpack/lib/action_view/base.rb:377:in `compile_and_render_template'
+    vendor/rails/actionpack/lib/action_view/base.rb:353:in `render_template'
+    vendor/rails/actionpack/lib/action_view/base.rb:303:in `render_file'
+    vendor/rails/actionpack/lib/action_controller/base.rb:1070:in `render_for_file'
+    vendor/rails/actionpack/lib/action_controller/base.rb:797:in `render_with_no_layout'
+    vendor/rails/actionpack/lib/action_controller/layout.rb:261:in `render_without_benchmark'
+    vendor/rails/actionpack/lib/action_controller/benchmarking.rb:51:in `render'
+    /usr/local/lib/ruby/1.8/benchmark.rb:293:in `measure'
+    vendor/rails/actionpack/lib/action_controller/benchmarking.rb:51:in `render'
+    vendor/rails/actionpack/lib/action_controller/base.rb:1125:in `perform_action_without_filters'
+    vendor/rails/actionpack/lib/action_controller/filters.rb:697:in `call_filters'
+    vendor/rails/actionpack/lib/action_controller/filters.rb:723:in `run_before_filters'
+    app/controllers/application.rb:174:in `set_context'
+    vendor/plugins/active_record_context/lib/technoweenie/active_record_context.rb:40:in `with_context'
+    app/controllers/application.rb:173:in `set_context'
+    vendor/rails/actionpack/lib/action_controller/filters.rb:471:in `send!'
+    vendor/rails/actionpack/lib/action_controller/filters.rb:471:in `call'
+    vendor/rails/actionpack/lib/action_controller/filters.rb:720:in `run_before_filters'
+    vendor/rails/actionpack/lib/action_controller/filters.rb:695:in `call_filters'
+    vendor/rails/actionpack/lib/action_controller/filters.rb:689:in `perform_action_without_benchmark'
+    vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
+    /usr/local/lib/ruby/1.8/benchmark.rb:293:in `measure'
+    vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
+    vendor/rails/actionpack/lib/action_controller/rescue.rb:175:in `perform_action_without_caching'
+    vendor/rails/actionpack/lib/action_controller/caching.rb:670:in `perform_action'
+    vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in `cache'
+    vendor/rails/activerecord/lib/active_record/query_cache.rb:8:in `cache'
+    vendor/rails/actionpack/lib/action_controller/caching.rb:669:in `perform_action'
+    vendor/rails/actionpack/lib/action_controller/base.rb:517:in `send'
+    vendor/rails/actionpack/lib/action_controller/base.rb:517:in `process_without_filters'
+    vendor/rails/actionpack/lib/action_controller/filters.rb:685:in `process_without_session_management_support'
+    vendor/rails/actionpack/lib/action_controller/session_management.rb:123:in `process'
+    vendor/rails/actionpack/lib/action_controller/base.rb:377:in `process'
+    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:170:in `handle_request'
+    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:114:in `dispatch'
+    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:125:in `dispatch_cgi'
+    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:9:in `dispatch'
+    /opt/lsws/fcgi-bin/RailsRunner.rb:24
+
+[code]Rendering /applied/warehouse/public/500.html (500 Internal Server Error)
+
+Any ideas?

data/test/fixtures/comment/ham/epic.txt

@@ -0,0 +1,35 @@
+Well, you asked for it... and it is long. :)  (Short version... stick with Lighthouse...)
+
+First, don't get me wrong, I love 37Signals' products.  I have (had) a paid account for every one of their subscription apps.  Currently, Backpack is my absolute favorite.  Since they opened it up to be multi-user, it is the perfect Intranet for a company.  However, I have always found Basecamp to be a little lacking for software projects.  The ToDo list feature isn't great for tracking that kind of work.  I am used to Issue Tracking systems like FogBugz, TestTrack Pro, JIRA, etc.  I like to record everything I can regarding each ticket (bug, feature, whatever it is).  Lighthouse has all the features you need for tracking a software development project, in a much more affordable package (compared to JIRA, Testrack Pro and FogBugz).  I like FogBugz a lot, but it can get expensive if you are developing on a team.  Lighthouse is just right... affordable, feature rich, nice to look at and easy to use.
+
+Compared to Basecamp, they both have a Dashboard, Overview pages for each project, Messages, Attachments and Milestones.  Obviously, the point at which they really diverge is task management.
+
+Tickets vs. Todos
+-----------------
+Lighthouse is Ticket-centric as you know.  You can track comments (history) with each ticket.  Tickets also track any state changes (like adding new tags, changing the ticket status, etc).  Basecamp's focus is equally distributed between all their objects.  Team collaboration is the main (published) focus behind Basecamp.  Basecamp's Todos are just 'one-liner' tasks that you can re-order and drag between lists.  There are no unique IDs (ticket #18), comments, notes or history.
+
+Pages vs. Writeboards
+---------------------
+Basecamp has Writeboards, however, they aren't tightly integrated since it redirects you out of the application to use them (but having the links is better than nothing).  Lighthouse has Pages, which are nice because they are right there in the project (no redirection).  Both Writeboards and Pages are like the Wikis of other systems (FogBugz)... a great place to write documentation.  I think Lighthouse does a little better job here, from the software development perspective.  The thing that bothers me about the redirection of Basecamp's Writeboards is the loss of the navigation.  You have to click 'Back to Project' then you can continue navigating.  It just seems unnecessary to me (but I understand why).  Both Pages and Writeboards are Textile-based but Writeboards do track your versions as you make edits to the documents.  Lighthouse doesn't, but I know it could since Rick literally wrote the "plugin":http://github.com/technoweenie/acts_as_versioned/tree/master. ;)  I wouldn't mind seeing Pages get their own sub-nav button beside Milestones (Overview >> Tickets >> Messages >> Milestones >> Pages).
+
+File Management/Attachments
+---------------------------
+I think Basecamp gets the file management part right.  You can attach files to Messages or upload them directly to the Files page and you can search and browse them.  They have a way to browse the image previews, etc.  Lighthouse can attach to messages, tickets and comments, but the images aren't displayed inline which I think would be a nice feature.  I sometimes don't realize the attachments are there because they get lost in the sidebar.  In Lighthouse, when you do click an image, it links directly to it.  I think it would be nice to have two links.  One to view it within the context of the page (using something like FancyZoom) and the other could continue to take you to a direct link to the image.  Or maybe you just hover over the link for a semi-large preview and clicking it remains the same.  But, once you get used to the existing setup, it works fine.
+
+RSS vs. Notifications
+---------------------
+The thing I need to remember about Lighthouse is that it is more RSS-focused.  Instead of notifications for things you create, they give you the RSS feeds.  Since I jumped into RSS later than most, that doesn't always occur to me right away.  But, now that I have subscribed to the feed, I can see what is going on just fine.  With Apple Mail, you can subscribe to an RSS feed and have it show up in your Inbox with your email (and Outlook 2007 too, I think).  So, it is essentially the same feature as direct notifications (just not targeted to specific users).
+
+Chat
+-----------
+Basecamp has Chat integration, but it is really just a link to a particular Campfire room in the previously setup Campfire account.  So, it isn't necessarily a 'feature'.  See below under "Lighthouse Enhancements" for more on this.
+
+Something cool I have setup is a 'webclip' of the Project list (from the Dashboard) and the History (also from the Dashboard).  (I also did this for my GitHub repository list.)  So, I can just press F12 on my Mac and see what is new on the site OR click a link right to a project or item.  It works great.  (But I got that idea from a blog post about doing the same thing with the Backpack Journal.) :)
+
+Lastly, I have always been into UI.  Justin has done a fantastic job with v2 of Lighthouse.  I love the fonts, the colors, the arrangement of positive/negative space...  I think it is absolutely fantastic on a Mac in Safari (or any combo, but that is my favorite).  Plus, when you couple Engine Yard hosting with Safari rendering speed, font smoothing on a Mac, and Justin's artistic ability, it is just a great user experience.  I find it to be an excellent, well-designed tool.  (The design of Basecamp is very nice too, clean and easy to use, but I like Lighthouse v2 better.)
+
+If I was you, I would stick with Lighthouse as your project management tool.  Basecamp is great for project management, but it is better for generic projects.
+
+Lighthouse Enhancements
+-----------------------
+Some feature requests for Lighthouse that would really tighten it up as a Software Development Project Management tool would be EITHER Message Notifications OR better explanation of the use of RSS to accomplish the same result.  I don't think it is readily apparent.  To most it would seem that Messages in Lighthouse just aren't as mature as Messages in Basecamp.  Second, it would be nice to have customizable 'Quick Links' in the sidebar or somewhere.  This would simply be a label field and a URL field (Target a new window, though).  That way, you could add links to other commonly used tools like Github, Campfire, Backpack, etc.  You could define them globally or on a per-project basis.  They would all show up in the Project sidebar, but the global links would appear in every project.  Finally, inline display of image attachments.  Little previews right beside the comments would be very nice.  I can recommend a great plugin called "attachment_fu":http://github.com/technoweenie/attachment_fu/tree/master for just such a job (ha!).

data/test/fixtures/comment/ham/epic_warehouse.txt

@@ -0,0 +1,92 @@
+I know nothing. You can blame it all on Dreamhost: they offered a very easy interface to setup subversion without having to do much of anything. The good part is that I was very easily able to set up subversion and use it. I found it awesome for writing paper drafts and for the light programming I do. This subversion experience allowed  me to see the value in Warehouse. The bad news is that this means somebody with virtually no terminal or Rails experience (me!) is trying install Warehouse, and the installation instructions are definitely NOT written in a way individuals like me can fully understand. Certain parts seem like complete gibberish.
+
+So here's my attempt to document what a complete Terminal/Rails/Server novice needs to do to get Warehouse running on a Dreamhost server using OS X. I primarily need somebody to tell me if what I've outlined so far is correct, and to tell me specifically what to do for the parts where I'm lost. I'm hoping that with your help this thread can serve as a reference for any other novices like myself who would like to get this up and running.
+
+PART 1: Installing Warehouse on Dreamhost
+
+For this section, follow along with the page:
+http://warehouseapp.com/installing/warehouse-on-dreamhost
+
+1) Follow the instructions to setup a fully hosted domain through Dreamhost. For most people this means setting up a new subdomain. This is easily done through dreamhost's control panel. The only tricky bit here is that you will need to fill out a support certificate and ask Dreamhost to allow wildcards on this specific domain you setup. Just fill out a support request through the dreamhost control panel. It's one of the drop down menus in their support. Literally just say "I need wildcards on "subdomain.domain.com" and they should be able to get it working pretty fast.
+
+2) Here is where the hard stuff starts. 
+
+a) You need to "unzip Warehouse in the appropriate directory". What is the appropriate directory? I don't know, but I assume it's the root directory of the subdomain just created (HELP!). Now, when they say unzip in the appropriate directory they mean they want you to use TERMINAL to connect to the dreamhost server and use UNIX commands. The use of the terminal is going to be unavoidable in this process, but you can avoid it at this step if you'd like. The easy way (for people not familiar with the UNIX) is to just unzip the file in OS X and just FTP the folder to your new subdomain using your favorite FTP client. Whether you should ftp the entire "warehouse" folder or just it's contents: I'm not sure. (I actually used ftp to upload the .gz file, which I then used the terminal to unzip, and then I had to unzip the .tar file (I'm trying to learn as I go). I ended up with the warehouse folder in the root directory of the subdomain).
+
+b) Second, they want you to edit THREE files in this folder. The wording makes it seem like two, but it is really three. They are all located in "warehouse-1.0.4/public". Open them in some form of text editor and do the edits they specify (keeping with the FTP theme you can do this directly on the server with Transmit or Interarchy. Otherwise you are going to need to download the file, open with textedit, edit it, save it (make sure as plain text!), then re-upload the file). I  have no clue how to do this stuff directly through the terminal, but I realize that's how the cool kids do it.
+
+For both the "dispatch.rb" and "dispatch.fcgi" files, type in as a new line (make this the very first line on the file)
+
+ /usr/local/bin/ruby
+
+Just type this in as a new line and don't replace/overwrite/delete anything. For the ".htaccess" file, follow the directions they outline. Not sure why the give specific directions for only one of the three files. I guess it's obvious if you aren't clueless like me.
+
+3) Now you are going to be forced to use TERMINAL to check if you did this right. There's no avoiding it now: fire up the TERMINAL program (it's found in "Applications/utilities" on your computer) and type 
+
+ssh username@domain.com
+
+Username refers to your username to access the server (given to you by Dreamhost). Domain is your domain name with dreamhost. You'll then be asked for the password (also originally given to you by Dreamhost). If you get no error type:
+
+irb 
+
+which starts some form program and then type 
+
+require 'svn/core' 
+
+if it says "true", you did it! Type
+
+exit
+
+ to get out of irb (whatever that is)
+
+
+PART 2: Connecting to the Database!
+Okay, now you need to follow the standard installation instructions. Follow along with this page:
+http://warehouseapp.com/installing/installing-and-registering-warehouse
+
+1) The first thing you'll need to do is to setup a database for Warehouse to use. Do this from the "goodies -> manageMySQL" menu on in the Dreamhost control panel. 
+
+a) Database Name: whatever
+
+b) Hostname: you'll probably need to set-up a new hostname for the database. It's kind of confusing because it acts an awful lot like creating a subdomain, but it's not the same. AFAIK you can call the hostname whatever you want as it makes no difference to anything (other than your own organization). You'll end up with something like "database.domain.com". 
+
+c) User/Password info: whatever you want. Just keep note of them for future use.
+
+2) Okay, now you need to go back into TERMINAL and navigate to the root directory of Warehouse. This assumes you are still "connected" from that ssh business you just did. If not, just redo that part. Now, depending on how you unzipped, you might not need to do anything. If you dragged the warehouse folder CONTENTS to the server, don't do anything. If you dragged the folder (or the zip file and you unzipped on the server) type
+
+ls
+
+this will show you the name of any folder in the directory. Type 
+
+cd foldername
+
+where "foldername" is whatever folder 'ls' told you (probably "warehouse-1.0.4")
+
+now type
+
+rake warehouse:bootstrap
+
+Now it's going to ask you a bunch of questions:
+
+a) For "Host Name" type the host name you gave to dreamhost for your database.
+b) For "Database name" do the same (whatever you told dreamhost earlier)
+c) For "username", do the same
+d) For "password", do the same
+e) For "socket path" do nothing (just hit enter). I have no idea what this is.
+f) Answer "y" to the question and press enter
+
+A bunch of stuff flies by and hopefully at the end it says "Warehouse is ready to roll
+
+PART 3: FINALLY INSTALLING WAREHOUSE
+
+Now it wants you to use the terminal (I think) to navigate to a webpage using RUBY (I think). Type:
+
+script/server
+
+to launch some program. Now... I don't know what to do here. There's some syntax to navigate to a page but typing my warehouse domain address does nothing. So close, so close....
+
+Any help?
+
+(Bonus question: does Warehouse play well with the simple subversion setup Dreamhost has?)
+
+Thanks in advance!