Empact-ec2onrails 0.9.9

data/lib/ec2onrails/version.rb

@@ -0,0 +1,31 @@
+#    This file is part of EC2 on Rails.
+#    http://rubyforge.org/projects/ec2onrails/
+#
+#    Copyright 2007 Paul Dowman, http://pauldowman.com/
+#
+#    EC2 on Rails is free software; you can redistribute it and/or modify
+#    it under the terms of the GNU General Public License as published by
+#    the Free Software Foundation; either version 2 of the License, or
+#    (at your option) any later version.
+#
+#    EC2 on Rails is distributed in the hope that it will be useful,
+#    but WITHOUT ANY WARRANTY; without even the implied warranty of
+#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+#    GNU General Public License for more details.
+#
+#    You should have received a copy of the GNU General Public License
+#    along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+module Ec2onrails #:nodoc:
+  module VERSION #:nodoc:
+    MAJOR = 0
+    MINOR = 9
+    TINY  = 9
+    # GEM_UPDATE  = 0
+    # STRING = [MAJOR, MINOR, TINY, GEM_UPDATE].join('.')
+    STRING = [MAJOR, MINOR, TINY].join('.')
+    
+    AMI_ID_32_BIT = 'ami-c9bc58a0'
+    AMI_ID_64_BIT = 'ami-cbbc58a2'
+  end
+end

data/test/autobench.conf

@@ -0,0 +1,60 @@
+# Autobench Configuration File
+
+# host1, host2
+# The hostnames of the servers under test
+# Eg. host1 = iis.test.com
+#     host2 = apache.test.com
+
+file = out.tsv
+
+host1 = ec2-67-202-61-243.compute-1.amazonaws.com
+
+# uri1, uri2
+# The URI to test (relative to the document root).  For a fair comparison
+# the files should be identical (although the paths to them may differ on the
+# different hosts)
+
+uri1  = /
+
+# port1, port2
+# The port number on which the servers are listening
+
+port1 = 80
+
+# low_rate, high_rate, rate_step
+# The 'rate' is the number of number of connections to open per second.
+# A series of tests will be conducted, starting at low rate,
+# increasing by rate step, and finishing at high_rate.
+# The default settings test at rates of 20,30,40,50...180,190,200
+
+low_rate  = 1
+high_rate = 5
+rate_step = 1
+
+# num_conn, num_call
+# num_conn is the total number of connections to make during a test
+# num_call is the number of requests per connection
+# The product of num_call and rate is the the approximate number of
+# requests per second that will be attempted.
+
+num_conn  = 1000
+num_call  = 5
+
+# timeout sets the maximimum time (in seconds) that httperf will wait
+# for replies from the web server.  If the timeout is exceeded, the
+# reply concerned is counted as an error.
+
+timeout   = 10
+
+# output_fmt
+# sets the output type - may be either "csv", or "tsv";
+
+output_fmt = tsv
+
+## Config for distributed autobench (autobench_admin)
+# clients
+# comma separated list of the hostnames and portnumbers for the
+# autobench clients.  No whitespace can appear before or after the commas.
+# clients = bench1.foo.com:4600,bench2.foo.com:4600,bench3.foo.com:4600
+
+#clients = localhost:4600

data/test/spec/lib/s3_helper_spec.rb

@@ -0,0 +1,134 @@
+require 'spec'
+require "#{File.dirname(__FILE__)}/../../../server/files/usr/local/ec2onrails/lib/s3_helper"
+
+REAL_S3_CONFIG = "#{File.dirname(__FILE__)}/../../../../local/s3.yml"
+MOCK_S3_CONFIG = "#{File.dirname(__FILE__)}/../../../examples/s3.yml"
+
+TEST_FILE_1 = "#{File.dirname(__FILE__)}/../test_files/test1"
+TEST_FILE_2 = "#{File.dirname(__FILE__)}/../test_files/test2"
+
+describe Ec2onrails::S3Helper do
+  before(:each) do
+    FileUtils.rm_f("/tmp/test*")
+  end
+
+  describe "with a mock connection" do
+    before(:each) do
+      AWS::S3::Base.stub!(:establish_connection!)
+      @s3_helper = Ec2onrails::S3Helper.new("bucket", nil, MOCK_S3_CONFIG, "production")
+    end
+
+    it "can load S3 config details from a config file with multiple environment sections" do
+      @s3_helper.aws_access_key.should == "DEF456"
+      @s3_helper.aws_secret_access_key.should == "def456def456def456def456"
+      @s3_helper.bucket.should == "yourbucket-bucket"
+    end
+
+    it "can load S3 config details from a config file with no environment sections" do
+      s3 = Ec2onrails::S3Helper.new("bucket", nil, "#{File.dirname(__FILE__)}/s3_old.yml", "production")
+      s3.aws_access_key.should == "ABC123"
+      s3.aws_secret_access_key.should == "abc123abc123abc123abc123"
+      s3.bucket.should == "yourbucket-bucket"
+    end
+
+    it "can create an s3 key using a given filename" do
+      @s3_helper.s3_key(TEST_FILE_1).should == "test1"
+    end
+
+    it "can create an s3 key using a given filename and a subdir name" do
+      @s3_helper = Ec2onrails::S3Helper.new("bucket", "subdir", MOCK_S3_CONFIG, "production")
+      @s3_helper.s3_key(TEST_FILE_1).should == "subdir/test1"
+    end
+  end
+
+  describe "with a real connection" do
+    # Integration tests to make sure we can use the real API
+    before(:each) do
+      @s3_helper = Ec2onrails::S3Helper.new("ec2onrails-test", nil, REAL_S3_CONFIG, "production")
+      begin
+        bucket = AWS::S3::Bucket.find(@s3_helper.bucket)
+        bucket.delete_all
+        # bucket.delete
+      rescue AWS::S3::NoSuchBucket
+        # no problem
+      end
+    end
+
+    it "can create a bucket" do
+      @s3_helper.create_bucket
+      AWS::S3::Bucket.find(@s3_helper.bucket)
+    end
+
+    it "can upload a file to S3" do
+      @s3_helper.store_file(TEST_FILE_1)
+      AWS::S3::S3Object.find("test1", "ec2onrails-test")
+    end
+
+    it "can upload a file to S3 into a subdir" do
+      @s3_helper = Ec2onrails::S3Helper.new("test", "subdir", REAL_S3_CONFIG, "production")
+      @s3_helper.store_file(TEST_FILE_1)
+      AWS::S3::S3Object.find("subdir/test1", "ec2onrails-test")
+    end
+
+    it "can retrieve a file from S3" do
+      @s3_helper.store_file(TEST_FILE_1)
+      AWS::S3::S3Object.find("test1", "ec2onrails-test")
+    end
+
+    it "can retrieve a file from S3 into a subdir" do
+      @s3_helper = Ec2onrails::S3Helper.new("test", "subdir", REAL_S3_CONFIG, "production")
+      @s3_helper.store_file(TEST_FILE_1)
+      @s3_helper.retrieve_file("/tmp/test1")
+    end
+
+    it "can delete files with a given prefix" do
+      @s3_helper.store_file(TEST_FILE_1)
+      @s3_helper.store_file(TEST_FILE_2)
+      AWS::S3::S3Object.find("test1", "ec2onrails-test")
+      AWS::S3::S3Object.find("test2", "ec2onrails-test")
+      @s3_helper.delete_files("test")
+      lambda {
+        AWS::S3::S3Object.find("test1", "ec2onrails-test")
+      }.should raise_error
+      lambda {
+        AWS::S3::S3Object.find("test2", "ec2onrails-test")
+      }.should raise_error
+    end
+
+    it "can delete files with a given prefix in a subdir" do
+      @s3_helper = Ec2onrails::S3Helper.new("test", "subdir", REAL_S3_CONFIG, "production")
+      @s3_helper.store_file(TEST_FILE_1)
+      @s3_helper.store_file(TEST_FILE_2)
+      AWS::S3::S3Object.find("subdir/test1", "ec2onrails-test")
+      AWS::S3::S3Object.find("subdir/test2", "ec2onrails-test")
+      @s3_helper.delete_files("test")
+      lambda {
+        AWS::S3::S3Object.find("subdir/test1", "ec2onrails-test")
+      }.should raise_error
+      lambda {
+        AWS::S3::S3Object.find("subdir/test2", "ec2onrails-test")
+      }.should raise_error
+    end
+
+    it "can retrieve files with a given prefix into a local dir" do
+      @s3_helper.store_file(TEST_FILE_1)
+      @s3_helper.store_file(TEST_FILE_2)
+      AWS::S3::S3Object.find("test1", "ec2onrails-test")
+      AWS::S3::S3Object.find("test2", "ec2onrails-test")
+      @s3_helper.retrieve_files("test", "/tmp")
+      File.exists?("/tmp/test1").should be_true
+      File.exists?("/tmp/test2").should be_true
+    end
+
+    it "can retrieve files with a given prefix in a subdir into a local dir" do
+      @s3_helper = Ec2onrails::S3Helper.new("test", "subdir", REAL_S3_CONFIG, "production")
+      @s3_helper.store_file(TEST_FILE_1)
+      @s3_helper.store_file(TEST_FILE_2)
+      AWS::S3::S3Object.find("subdir/test1", "ec2onrails-test")
+      AWS::S3::S3Object.find("subdir/test2", "ec2onrails-test")
+      @s3_helper.retrieve_files("test", "/tmp")
+      File.exists?("/tmp/test1").should be_true
+      File.exists?("/tmp/test2").should be_true
+    end
+  end
+end

data/test/spec/lib/s3_old.yml

@@ -0,0 +1,3 @@
+aws_access_key: ABC123
+aws_secret_access_key: abc123abc123abc123abc123
+bucket_base_name: yourbucket

data/test/test_app/Capfile

@@ -0,0 +1,3 @@
+load 'deploy' if respond_to?(:namespace) # cap2 differentiator
+load 'config/deploy'
+require 'ec2onrails/recipes'

data/test/test_app/README

@@ -0,0 +1,182 @@
+== Welcome to Rails
+
+Rails is a web-application and persistence framework that includes everything
+needed to create database-backed web-applications according to the
+Model-View-Control pattern of separation. 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 rails command
+   and your application name. Ex: rails myapp
+   (If you've downloaded rails in a complete tgz or zip, this step is already done)
+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 and lighttpd if they are installed, otherwise
+Rails will use the WEBrick, the webserver that ships with Ruby. When you run script/server,
+Rails will check if Mongrel exists, then lighttpd and finally fall back to WEBrick. This ensures
+that you can always get up and running quickly.
+
+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
+
+If Mongrel is not installed, Rails will look for lighttpd. It's considerably faster than
+Mongrel and WEBrick and also suited for production use, but requires additional
+installation and currently only works well on OS X/Unix (Windows users are encouraged
+to start with Mongrel). We recommend version 1.4.11 and higher. You can download it from
+http://www.lighttpd.net.
+
+And finally, if neither Mongrel or lighttpd are installed, Rails will use the built-in Ruby
+web server, WEBrick. WEBrick is a small Ruby web server suitable for development, but not
+for production.
+
+But of course its also possible to run Rails on any platform that supports FCGI.
+Apache, LiteSpeed, IIS are just a few. For more information on FCGI,
+please visit: http://wiki.rubyonrails.com/rails/pages/FastCGI
+
+
+== Debugging Rails
+
+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.
+
+
+== Breakpoints
+
+Breakpoint support is available through the script/breakpointer client. This
+means that you can break out of execution at any point in the code, investigate
+and change the model, AND then resume execution! Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.find(:all)
+      breakpoint "Breaking out from the list"
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the breakpointer window. Here you can do things like:
+
+Executing breakpoint "Breaking out from the list" at .../webrick_server.rb:16 in 'breakpoint'
+
+  >> @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 breakpoint"
+  => "hello from a breakpoint"
+
+...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 press CTRL-D
+
+
+== 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>
+
+To reload your controllers and models after launching the console run <tt>reload!</tt>
+
+
+
+== 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.rhtml 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.rhtml. Inside default.rhtml,
+  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.
+
+components
+  Self-contained mini-applications that can bundle together controllers, models, and views.
+
+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.
+  This directory is in the load path.

data/test/test_app/Rakefile

@@ -0,0 +1,10 @@
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+
+require(File.join(File.dirname(__FILE__), 'config', 'boot'))
+
+require 'rake'
+require 'rake/testtask'
+require 'rake/rdoctask'
+
+require 'tasks/rails'

data/test/test_app/app/controllers/application.rb

@@ -0,0 +1,7 @@
+# Filters added to this controller apply to all controllers in the application.
+# Likewise, all the methods added will be available for all controllers.
+
+class ApplicationController < ActionController::Base
+  # Pick a unique cookie name to distinguish our session data from others'
+  session :session_key => '_test_app_session_id'
+end