rackamole 0.2.5 → 0.2.6

data/tasks/setup.rb

@@ -21,7 +21,7 @@ PROJ = OpenStruct.new(
   :email => nil,
   :url => "\000",
   :version => ENV['VERSION'] || '0.0.0',
-  :exclude => %w(tmp$ bak$ ~$ CVS \.svn/ \.git/ ^pkg/),
+  :exclude => %w(tmp$ bak$ ~$ CVS \.svn/ \.git/ ^pkg/ samples/* z_experiments/* images/*),
   :release_name => ENV['RELEASE'],
 
   # System Defaults

data/tasks/test.rake

@@ -5,6 +5,7 @@ require 'rake/testtask'
 namespace :test do
 
   Rake::TestTask.new(:run) do |t|
+puts "YO"    
     t.libs = PROJ.libs
     t.test_files = if test(?f, PROJ.test.file) then [PROJ.test.file]
                    else PROJ.test.files end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: rackamole
 version: !ruby/object:Gem::Version 
-  version: 0.2.5
+  version: 0.2.6
 platform: ruby
 authors: 
 - Fernand Galiana
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-01-09 00:00:00 -07:00
+date: 2010-01-21 00:00:00 -07:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -102,17 +102,7 @@ dependencies:
       - !ruby/object:Gem::Version 
         version: 2.5.1
     version: 
-description: "The MOle is a rack application that monitors user interactions with your web site. We are not \n\
-  talking about counting page hits here. The MOle tracks all the information available to capture\n\
-  the essence of a user interaction with your application. Using the MOle, you are able to see\n\
-  which feature is a hit or a bust. As an added bonus, the MOle also track performance and exceptions \n\
-  that might have escaped your test suites or alpha env. To boot your managers will love you for it! \n\n\
-  Whether you are releasing a new application or improving on an old one, it is always a good thing \n\
-  to know if anyone is using your application and if they are, how they are using it. \n\
-  What features are your users most fond of and which features find their way into the abyss? \n\
-  You will be able to rapidly assess whether or not your application is a hit and if\n\
-  your coolest features are thought as such by your users. You will be able to elegantly record user\n\
-  interactions and leverage these findings for the next iteration of your application. "
+description: "  The MOle is a rack application that monitors user interactions with your web site. We are not \n  talking about counting page hits here. The MOle tracks all the information available to capture\n  the essence of a user interaction with your application. Using the MOle, you are able to see\n  which feature is a hit or a bust. As an added bonus, the MOle also track performance and exceptions \n  that might have escaped your test suites or alpha env. To boot your managers will love you for it! \n\n  Whether you are releasing a new application or improving on an old one, it is always a good thing \n  to know if anyone is using your application and if they are, how they are using it. \n  What features are your users most fond of and which features find their way into the abyss? \n  You will be able to rapidly assess whether or not your application is a hit and if\n  your coolest features are thought as such by your users. You will be able to elegantly record user\n  interactions and leverage these findings for the next iteration of your application. "
 email: fernand.galiana@gmail.com
 executables: []
 
@@ -120,20 +110,12 @@ extensions: []
 
 extra_rdoc_files: 
 - README.rdoc
-- aaa.txt
 - lib/rackamole/alert/templates/alert.erb
-- samples/rails/moled/public/robots.txt
 files: 
 - ...
 - HISTORY
 - README.rdoc
 - Rakefile
-- a.rb
-- aaa.txt
-- images/mole_logo.png
-- images/mole_logo.psd
-- images/mole_logo_small.png
-- images/mole_logo_small.psd
 - lib/rackamole.rb
 - lib/rackamole/alert/emole.rb
 - lib/rackamole/alert/templates/alert.erb
@@ -148,67 +130,6 @@ files:
 - lib/rackamole/store.rb
 - lib/rackamole/store/log.rb
 - lib/rackamole/store/mongo_db.rb
-- samples/rails/moled/README
-- samples/rails/moled/Rakefile
-- samples/rails/moled/app/controllers/application_controller.rb
-- samples/rails/moled/app/controllers/fred_controller.rb
-- samples/rails/moled/app/helpers/application_helper.rb
-- samples/rails/moled/app/views/fred/index.html.erb
-- samples/rails/moled/app/views/fred/show.html.erb
-- samples/rails/moled/config/boot.rb
-- samples/rails/moled/config/database.yml
-- samples/rails/moled/config/environment.rb
-- samples/rails/moled/config/environments/development.rb
-- samples/rails/moled/config/environments/production.rb
-- samples/rails/moled/config/environments/test.rb
-- samples/rails/moled/config/initializers/backtrace_silencers.rb
-- samples/rails/moled/config/initializers/inflections.rb
-- samples/rails/moled/config/initializers/mime_types.rb
-- samples/rails/moled/config/initializers/new_rails_defaults.rb
-- samples/rails/moled/config/initializers/session_store.rb
-- samples/rails/moled/config/locales/en.yml
-- samples/rails/moled/config/routes.rb
-- samples/rails/moled/db/development.sqlite3
-- samples/rails/moled/db/production.sqlite3
-- samples/rails/moled/doc/README_FOR_APP
-- samples/rails/moled/log/development.log
-- samples/rails/moled/log/production.log
-- samples/rails/moled/log/server.log
-- samples/rails/moled/log/test.log
-- samples/rails/moled/public/404.html
-- samples/rails/moled/public/422.html
-- samples/rails/moled/public/500.html
-- samples/rails/moled/public/favicon.ico
-- samples/rails/moled/public/images/rails.png
-- samples/rails/moled/public/index.html
-- samples/rails/moled/public/javascripts/application.js
-- samples/rails/moled/public/javascripts/controls.js
-- samples/rails/moled/public/javascripts/dragdrop.js
-- samples/rails/moled/public/javascripts/effects.js
-- samples/rails/moled/public/javascripts/prototype.js
-- samples/rails/moled/public/robots.txt
-- samples/rails/moled/script/about
-- samples/rails/moled/script/console
-- samples/rails/moled/script/dbconsole
-- samples/rails/moled/script/destroy
-- samples/rails/moled/script/generate
-- samples/rails/moled/script/performance/benchmarker
-- samples/rails/moled/script/performance/profiler
-- samples/rails/moled/script/plugin
-- samples/rails/moled/script/runner
-- samples/rails/moled/script/server
-- samples/rails/moled/test/performance/browsing_test.rb
-- samples/rails/moled/test/test_helper.rb
-- samples/sinatra/moled.rb
-- samples/sinatra/public/.DS_Store
-- samples/sinatra/public/images/mole_logo.png
-- samples/sinatra/public/stylesheets/styles.css
-- samples/sinatra/views/index.erb
-- samples/sinatra/views/layout.erb
-- samples/sinatra/views/normal.erb
-- samples/sinatra/views/params.erb
-- samples/sinatra/views/post.erb
-- samples/sinatra/views/slow.erb
 - spec/expected_results/mole_exception.log
 - spec/expected_results/mole_feature.log
 - spec/expected_results/mole_perf.log
@@ -238,9 +159,6 @@ files:
 - tasks/svn.rake
 - tasks/test.rake
 - tasks/zentest.rake
-- z_experiments/config.rb
-- z_experiments/config_sample.rb
-- z_experiments/configuration.rb
 has_rdoc: true
 homepage: http://www.rackamole.com
 licenses: []

data/a.rb

@@ -1,18 +0,0 @@
-require 'rubygems'
-require 'pony'
-
-# :to      => ['fernand.galiana@gmail.com', 'fernand@collectiveintellect.com'],
-
-result = Pony.mail( 
-  :from     => 'fernand@collectiveintellect.com',
-  :to      => 'fernand.galiana@gmail.com, fernand@collectiveintellect.com',
-  :subject => 'test5', 
-  :body    => "Hello World"
-  # :via     => :smtp,
-  # :smtp    => { :host => "exchange@collectiveintellect.com", :port => 25, : }
-  # :user    => 'fernand@collectiveintellect.com',
-  # :password => '$mistral1',
-  # :auth     => :plain
-)
-
-puts result.inspect

data/aaa.txt

@@ -1,52 +0,0 @@
-Information:
-
-* Fernand Galiana: fernand.galiana@gmail.com : @kitesufer
-* Rackamole: http://rackamole.com : @rackamole
-* Forum:     http://groups.google.com/group/rackamole
-* Git:       git://github.com/derailed/rackamole.git
-
-Rackamole: Observe your web applications in the wild...
-
-These days, companies love to claim their entire devotion to the Agile process. 
-We all iterate, do the SCRUM thing, often for longer than we care for, and we are 
-all sworn into delivering early and often... 
-
-But how can you really measure if your application is a success or a bust? 
-We all know that page hits and heat maps are only good in the eyes of marketeers, 
-or some usability PHD... How do you accurately assess that the "must have" features
-in your application are actually being used and how are your customers actually using them ? 
-More importantly, how can you accurately assess you are iterating down the right path for 
-your product and company success, and not simply digging further in the rat hole ?
-
-In other word, at times do you feel you are adhering to the frAgile methodology 
-whose motto is 'Deliver early and often deliver the wrong shit?
-
-Rackamole is a rack application that allows you to cover the 'death zone' in your application
-life cycle. Prior to your next iteration, why not take the time to observe the interactions of your 
-customers with your application in the wild. Rackmole specializes in trapping and recording 
-feature usage, performance issues and application exception. By being part and not seating
-outside your application stack, the mole can record the very essence of an interaction.
-You can then leverage this new found knowledge to prepare for your next iterations.
-As an added bonus, you can leverage Rackamole, to track your QA team progress and making sure  
-no features is left unturned prior to the big push.
-
-Installation:
-
-> gem install rackamole -s http://gemcutter.org
-
-Usage:
-
-use Rack::Mole, {...}
-
-You can simply log the interaction to the console (the default) or log file.
-Alternatively leverage the mongo adapter to use MongoDB to store the information 
-for later querying and reporting.
-
-The gem comes bundled with an email notifier to alert you when something is happening and 
-needs your attention. Granted this won't improve your social ranking much, but additionally 
-you and your team can follow your application 'happenings' on twitter...
-
-We are currently working on companion application aka 'Wackamole' that will allow you to view 
-and drilldown on the collected information.
-
-Thanks for stopping by!

data/samples/rails/moled/README

@@ -1,243 +0,0 @@
-== Welcome to Rails
-
-Rails is a web-application framework that includes everything needed to create 
-database-backed web applications according to the Model-View-Control pattern. 
-
-This pattern splits the view (also called the presentation) into "dumb" templates
-that are primarily responsible for inserting pre-built data in between HTML tags.
-The model contains the "smart" domain objects (such as Account, Product, Person,
-Post) that holds all the business logic and knows how to persist themselves to
-a database. The controller handles the incoming requests (such as Save New Account,
-Update Product, Show Post) by manipulating the model and directing data to the view.
-
-In Rails, the model is handled by what's called an object-relational mapping
-layer entitled Active Record. This layer allows you to present the data from
-database rows as objects and embellish these data objects with business logic
-methods. You can read more about Active Record in
-link:files/vendor/rails/activerecord/README.html.
-
-The controller and view are handled by the Action Pack, which handles both
-layers by its two parts: Action View and Action Controller. These two layers
-are bundled in a single package due to their heavy interdependence. This is
-unlike the relationship between the Active Record and Action Pack that is much
-more separate. Each of these packages can be used independently outside of
-Rails.  You can read more about Action Pack in
-link:files/vendor/rails/actionpack/README.html.
-
-
-== Getting Started
-
-1. At the command prompt, start a new Rails application using the <tt>rails</tt> command
-   and your application name. Ex: rails myapp
-2. Change directory into myapp and start the web server: <tt>script/server</tt> (run with --help for options)
-3. Go to http://localhost:3000/ and get "Welcome aboard: You're riding the Rails!"
-4. Follow the guidelines to start developing your application
-
-
-== Web Servers
-
-By default, Rails will try to use Mongrel if it's are installed when started with script/server, otherwise Rails will use WEBrick, the webserver that ships with Ruby. But you can also use Rails
-with a variety of other web servers.
-
-Mongrel is a Ruby-based webserver with a C component (which requires compilation) that is
-suitable for development and deployment of Rails applications. If you have Ruby Gems installed,
-getting up and running with mongrel is as easy as: <tt>gem install mongrel</tt>.
-More info at: http://mongrel.rubyforge.org
-
-Say other Ruby web servers like Thin and Ebb or regular web servers like Apache or LiteSpeed or
-Lighttpd or IIS. The Ruby web servers are run through Rack and the latter can either be setup to use
-FCGI or proxy to a pack of Mongrels/Thin/Ebb servers.
-
-== Apache .htaccess example for FCGI/CGI
-
-# General Apache options
-AddHandler fastcgi-script .fcgi
-AddHandler cgi-script .cgi
-Options +FollowSymLinks +ExecCGI
-
-# If you don't want Rails to look in certain directories,
-# use the following rewrite rules so that Apache won't rewrite certain requests
-# 
-# Example:
-#   RewriteCond %{REQUEST_URI} ^/notrails.*
-#   RewriteRule .* - [L]
-
-# Redirect all requests not available on the filesystem to Rails
-# By default the cgi dispatcher is used which is very slow
-# 
-# For better performance replace the dispatcher with the fastcgi one
-#
-# Example:
-#   RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
-RewriteEngine On
-
-# If your Rails application is accessed via an Alias directive,
-# then you MUST also set the RewriteBase in this htaccess file.
-#
-# Example:
-#   Alias /myrailsapp /path/to/myrailsapp/public
-#   RewriteBase /myrailsapp
-
-RewriteRule ^$ index.html [QSA]
-RewriteRule ^([^.]+)$ $1.html [QSA]
-RewriteCond %{REQUEST_FILENAME} !-f
-RewriteRule ^(.*)$ dispatch.cgi [QSA,L]
-
-# In case Rails experiences terminal errors
-# Instead of displaying this message you can supply a file here which will be rendered instead
-# 
-# Example:
-#   ErrorDocument 500 /500.html
-
-ErrorDocument 500 "<h2>Application error</h2>Rails application failed to start properly"
-
-
-== Debugging Rails
-
-Sometimes your application goes wrong.  Fortunately there are a lot of tools that
-will help you debug it and get it back on the rails.
-
-First area to check is the application log files.  Have "tail -f" commands running
-on the server.log and development.log. Rails will automatically display debugging
-and runtime information to these files. Debugging info will also be shown in the
-browser on requests from 127.0.0.1.
-
-You can also log your own messages directly into the log file from your code using
-the Ruby logger class from inside your controllers. Example:
-
-  class WeblogController < ActionController::Base
-    def destroy
-      @weblog = Weblog.find(params[:id])
-      @weblog.destroy
-      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
-    end
-  end
-
-The result will be a message in your log file along the lines of:
-
-  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1
-
-More information on how to use the logger is at http://www.ruby-doc.org/core/
-
-Also, Ruby documentation can be found at http://www.ruby-lang.org/ including:
-
-* The Learning Ruby (Pickaxe) Book: http://www.ruby-doc.org/docs/ProgrammingRuby/
-* Learn to Program: http://pine.fm/LearnToProgram/  (a beginners guide)
-
-These two online (and free) books will bring you up to speed on the Ruby language
-and also on programming in general.
-
-
-== Debugger
-
-Debugger support is available through the debugger command when you start your Mongrel or
-Webrick server with --debugger. This means that you can break out of execution at any point
-in the code, investigate and change the model, AND then resume execution! 
-You need to install ruby-debug to run the server in debugging mode. With gems, use 'gem install ruby-debug'
-Example:
-
-  class WeblogController < ActionController::Base
-    def index
-      @posts = Post.find(:all)
-      debugger
-    end
-  end
-
-So the controller will accept the action, run the first line, then present you
-with a IRB prompt in the server window. Here you can do things like:
-
-  >> @posts.inspect
-  => "[#<Post:0x14a6be8 @attributes={\"title\"=>nil, \"body\"=>nil, \"id\"=>\"1\"}>,
-       #<Post:0x14a6620 @attributes={\"title\"=>\"Rails you know!\", \"body\"=>\"Only ten..\", \"id\"=>\"2\"}>]"
-  >> @posts.first.title = "hello from a debugger"
-  => "hello from a debugger"
-
-...and even better is that you can examine how your runtime objects actually work:
-
-  >> f = @posts.first
-  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
-  >> f.
-  Display all 152 possibilities? (y or n)
-
-Finally, when you're ready to resume execution, you enter "cont"
-
-
-== Console
-
-You can interact with the domain model by starting the console through <tt>script/console</tt>.
-Here you'll have all parts of the application configured, just like it is when the
-application is running. You can inspect domain models, change values, and save to the
-database. Starting the script without arguments will launch it in the development environment.
-Passing an argument will specify a different environment, like <tt>script/console production</tt>.
-
-To reload your controllers and models after launching the console run <tt>reload!</tt>
-
-== dbconsole
-
-You can go to the command line of your database directly through <tt>script/dbconsole</tt>.
-You would be connected to the database with the credentials defined in database.yml.
-Starting the script without arguments will connect you to the development database. Passing an
-argument will connect you to a different database, like <tt>script/dbconsole production</tt>.
-Currently works for mysql, postgresql and sqlite.
-
-== Description of Contents
-
-app
-  Holds all the code that's specific to this particular application.
-
-app/controllers
-  Holds controllers that should be named like weblogs_controller.rb for
-  automated URL mapping. All controllers should descend from ApplicationController
-  which itself descends from ActionController::Base.
-
-app/models
-  Holds models that should be named like post.rb.
-  Most models will descend from ActiveRecord::Base.
-
-app/views
-  Holds the template files for the view that should be named like
-  weblogs/index.html.erb for the WeblogsController#index action. All views use eRuby
-  syntax.
-
-app/views/layouts
-  Holds the template files for layouts to be used with views. This models the common
-  header/footer method of wrapping views. In your views, define a layout using the
-  <tt>layout :default</tt> and create a file named default.html.erb. Inside default.html.erb,
-  call <% yield %> to render the view using this layout.
-
-app/helpers
-  Holds view helpers that should be named like weblogs_helper.rb. These are generated
-  for you automatically when using script/generate for controllers. Helpers can be used to
-  wrap functionality for your views into methods.
-
-config
-  Configuration files for the Rails environment, the routing map, the database, and other dependencies.
-
-db
-  Contains the database schema in schema.rb.  db/migrate contains all
-  the sequence of Migrations for your schema.
-
-doc
-  This directory is where your application documentation will be stored when generated
-  using <tt>rake doc:app</tt>
-
-lib
-  Application specific libraries. Basically, any kind of custom code that doesn't
-  belong under controllers, models, or helpers. This directory is in the load path.
-
-public
-  The directory available for the web server. Contains subdirectories for images, stylesheets,
-  and javascripts. Also contains the dispatchers and the default HTML files. This should be
-  set as the DOCUMENT_ROOT of your web server.
-
-script
-  Helper scripts for automation and generation.
-
-test
-  Unit and functional tests along with fixtures. When using the script/generate scripts, template
-  test files will be generated for you and placed in this directory.
-
-vendor
-  External libraries that the application depends on. Also includes the plugins subdirectory.
-  If the app has frozen rails, those gems also go here, under vendor/rails/.
-  This directory is in the load path.