condo 1.0.6 → 2.0.0

data/lib/condo/strata/rackspace_cloud_files.rb

@@ -1,245 +0,0 @@
-module Condo; end
-module Condo::Strata; end
-
-#
-# NOTE:: Set Account Metadata Key for Public Access before this will work - X-Account-Meta-Temp-Url-Key: <your key>
-#
-
-class Condo::Strata::RackspaceCloudFiles
-	
-	def initialize(options)
-		@options = {
-			:name => :RackspaceCloudFiles,
-			:location => :dfw,			# dallas or chicago	- this is set at bucket creation time
-			:fog => {
-				:provider => 'Rackspace',
-				:rackspace_username => options[:username],
-				:rackspace_api_key => options[:secret_key],
-				:rackspace_auth_url => options[:auth_url] || 'https://identity.api.rackspacecloud.com/v2.0' # is US and UK is 'lon.auth.api.rackspacecloud.com'
-			}
-		}.merge!(options)
-		
-		
-		@options[:location] = case @options[:location]
-			when :dfw, :dallas, :DFW then 'storage101.dfw1.clouddrive.com'
-			when :ord, :chicago, :ORD then 'storage101.ord1.clouddrive.com'
-		end
-		
-		
-		#raise ArgumentError, 'Rackspace Username missing' if @options[:username].nil?
-		#raise ArgumentError, 'Rackspace Secret Key missing' if @options[:secret_key].nil?
-		
-		raise ArgumentError, 'Rackspace Storage URL missing' if @options[:storage_url].nil?
-		raise ArgumentError, 'Rackspace Temp URL Key missing' if @options[:temp_url_key].nil?
-		
-		
-		@options[:location] = @options[:location].to_sym
-	end
-	
-	
-	def name
-		@options[:name]
-	end
-	
-	
-	def location
-		@options[:location]
-	end
-	
-	
-	#
-	# Here for convenience 
-	#
-	def set_metadata_key(key)
-		fog_connection.request(
-			:expects  => [201, 202, 204],
-			:method   => 'POST',
-			:headers  => {'X-Account-Meta-Temp-Url-Key' => key}
-		)
-	end
-	
-	
-	def allow_cors(domains = 'http://localhost:3000', options_age = 10, headers = 'etag, x-object-manifest, content-type, accept, origin, x-requested-with')
-		fog_connection.request(
-			:expects  => [201, 202, 204],
-			:method   => 'POST',
-			:headers  => {
-				'X-Container-Meta-Access-Control-Allow-Origin' => domains,
-				'X-Container-Meta-Access-Control-Max-Age' => options_age,
-				'X-Container-Meta-Access-Control-Allow-Headers' => headers
-			}
-		)
-	end
-	
-	
-	#
-	# Create a signed URL for accessing a private file
-	#
-	def get_object(options)
-		options = {}.merge!(options)	# Need to deep copy here
-		options[:object_options] = {
-			:expires => 5.minutes.from_now,
-			:verb => :get,		# Post for multi-part uploads http://docs.amazonwebservices.com/AmazonS3/latest/API/mpUploadInitiate.html
-			:headers => {},
-			:parameters => {}
-		}.merge!(options[:object_options] || {})
-		options.merge!(@options)
-		
-		#
-		# provide the signed request
-		#
-		sign_request(options)[:url]
-	end
-	
-	
-	#
-	# Creates a new upload request (either single shot or multi-part)
-	# => Passed: bucket_name, object_key, object_options, file_size
-	#
-	def new_upload(options)
-		options = {}.merge!(options)	# Need to deep copy here
-		options[:object_options] = {
-			:expires => 5.minutes.from_now,
-			:verb => :put,
-			:headers => {},
-			:parameters => {}
-		}.merge!(options[:object_options])
-		options.merge!(@options)
-		
-		options[:object_options][:headers]['ETag'] = options[:file_id] if options[:file_id].present? && options[:object_options][:headers]['ETag'].nil?
-		options[:object_options][:headers]['Content-Type'] = 'binary/octet-stream' if options[:object_options][:headers]['Content-Type'].nil?
-		
-		
-		#
-		# Decide what type of request is being sent
-		#
-		request = {}
-		if options[:file_size] > 2097152	# 2 mb (minimum chunk size)
-			
-			options[:object_key] = options[:object_key] + '_p1'		# Append the part number
-			request[:type] = :chunked_upload
-		else
-			
-			request[:type] = :direct_upload
-		end
-		
-		#
-		# provide the signed request
-		#
-		request[:signature] = sign_request(options)
-		request
-	end
-	
-	
-	#
-	# Returns the part we are up to
-	#
-	def get_parts(options)
-		{
-			:type => :parts,
-			:current_part => options[:resumable_id]
-		}
-	end
-	
-	
-	#
-	# Returns the requests for uploading parts and completing a resumable upload
-	#
-	def set_part(options)
-		options[:object_options] = {
-			:expires => 5.minutes.from_now,
-			:headers => {},
-			:parameters => {},
-			:verb => :put
-		}.merge!(options[:object_options])
-		options.merge!(@options)
-		
-		
-		request = {}
-		if options[:part] == 'finish'
-			#
-			# Send the commitment response
-			#
-			options[:object_options][:headers]['X-Object-Manifest'] = "#{options[:bucket_name]}/#{options[:object_key]}"
-			request[:type] = :finish
-		else
-			#
-			# Send the part upload request
-			#
-			options[:object_options][:headers]['ETag'] = options[:file_id] if options[:file_id].present? && options[:object_options][:headers]['ETag'].nil?
-			options[:object_options][:headers]['Content-Type'] = 'binary/octet-stream' if options[:object_options][:headers]['Content-Type'].nil?
-			options[:object_key] = options[:object_key] + '_p' + options[:part]
-			request[:type] = :part_upload
-		end
-		
-		#
-		# provide the signed request
-		#
-		request[:signature] = sign_request(options)
-		request
-	end
-	
-	
-	def fog_connection
-		@fog = @fog || Fog::Storage.new(@options[:fog])
-		return @fog
-	end
-	
-	
-	def destroy(upload)
-		connection = fog_connection
-		directory = connection.directories.get(upload.bucket_name)	# it is assumed this exists - if not then the upload wouldn't have taken place
-		
-		if upload.resumable
-			directory.files.all({'prefix' => upload.object_key}).each do |file|
-				return false unless file.destroy
-			end
-		end
-		
-		file = directory.files.get(upload.object_key)	# this is the manifest when resumable
-		
-		return true if file.nil?
-		return file.destroy
-	end
-	
-	
-	
-	protected
-	
-	
-	
-	def sign_request(options)
-		
-		#
-		# Build base URL
-		#
-		options[:object_options][:expires] = options[:object_options][:expires].utc.to_i
-		url = "/v1/#{options[:storage_url]}/#{CGI::escape options[:bucket_name]}/#{CGI::escape options[:object_key]}"
-		
-		
-		
-		#
-		# Build a request signature
-		#
-		signature = "#{options[:object_options][:verb].to_s.upcase}\n#{options[:object_options][:expires]}\n#{url}"
-		
-		
-		#
-		# Encode the request signature
-		#
-		signature = OpenSSL::HMAC.hexdigest('sha1', @options[:temp_url_key], signature)
-		
-		
-		#
-		# Finish building the request
-		#
-		return {
-			:verb => options[:object_options][:verb].to_s.upcase,
-			:url => "https://#{@options[:location]}#{url}?temp_url_sig=#{signature}&temp_url_expires=#{options[:object_options][:expires]}",
-			:headers => options[:object_options][:headers]
-		}
-	end
-	
-	
-end
-

data/test/condo_test.rb

@@ -1,27 +0,0 @@
-require 'test_helper'
-
-class CondoTest < ActiveSupport::TestCase
-	test "truth" do
-		assert_kind_of Module, Condo
-	end
-	
-	#
-	# Uses the example from the bottom of the page: http://s3.amazonaws.com/doc/s3-developer-guide/RESTAuthentication.html
-	#
-	test "AmazonS3 basic request signing" do
-		s3 = Condo::Strata::AmazonS3.new({
-			:access_id => '44CF9590006BF252F707',
-			:secret_key => 'OtxrzxIsfpFjA7SwPzILwy8Bw21TLhquhboDYROV'
-		})
-		
-		result = s3.get_object({
-			:bucket_name => 'quotes',
-			:object_key => 'nelson',
-			:object_options => {
-				:expires => Time.at(1141889120)
-			}
-		})
-		
-		assert (result == 'https://s3.amazonaws.com/quotes/nelson?AWSAccessKeyId=44CF9590006BF252F707&Expires=1141889120&Signature=vjbyPxybdZaNmGa%2ByT272YEAiv4%3D'), "Generated signature mismatch"
-	end
-end

data/test/dummy/README.rdoc

@@ -1,261 +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, create a new Rails application:
-       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
-
-2. Change directory to <tt>myapp</tt> and start the web server:
-       <tt>cd myapp; rails server</tt> (run with --help for options)
-
-3. Go to http://localhost:3000/ and you'll see:
-       "Welcome aboard: You're riding Ruby on Rails!"
-
-4. Follow the guidelines to start developing your application. You can find
-the following resources handy:
-
-* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
-* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
-
-
-== 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/. There are
-several books available online as well:
-
-* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
-* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
-
-These two 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 <tt>sudo gem install ruby-debug</tt>. Example:
-
-  class WeblogController < ActionController::Base
-    def index
-      @posts = Post.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", "body"=>"Only ten..", "id"=>"2"}>]"
-  >> @posts.first.title = "hello from a debugger"
-  => "hello from a debugger"
-
-...and even better, 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 can enter "cont".
-
-
-== Console
-
-The console is a Ruby shell, which allows you to interact with your
-application's domain model. 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.
-
-To start the console, run <tt>rails console</tt> from the application
-directory.
-
-Options:
-
-* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
-  made to the database.
-* Passing an environment name as an argument will load the corresponding
-  environment. Example: <tt>rails console production</tt>.
-
-To reload your controllers and models after launching the console run
-<tt>reload!</tt>
-
-More information about irb can be found at:
-link:http://www.rubycentral.org/pickaxe/irb.html
-
-
-== dbconsole
-
-You can go to the command line of your database directly through <tt>rails
-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>rails dbconsole production</tt>. Currently works for MySQL,
-PostgreSQL and SQLite 3.
-
-== Description of Contents
-
-The default directory structure of a generated Ruby on Rails application:
-
-  |-- app
-  |   |-- assets
-  |       |-- images
-  |       |-- javascripts
-  |       `-- stylesheets
-  |   |-- controllers
-  |   |-- helpers
-  |   |-- mailers
-  |   |-- models
-  |   `-- views
-  |       `-- layouts
-  |-- config
-  |   |-- environments
-  |   |-- initializers
-  |   `-- locales
-  |-- db
-  |-- doc
-  |-- lib
-  |   `-- tasks
-  |-- log
-  |-- public
-  |-- script
-  |-- test
-  |   |-- fixtures
-  |   |-- functional
-  |   |-- integration
-  |   |-- performance
-  |   `-- unit
-  |-- tmp
-  |   |-- cache
-  |   |-- pids
-  |   |-- sessions
-  |   `-- sockets
-  `-- vendor
-      |-- assets
-          `-- stylesheets
-      `-- plugins
-
-app
-  Holds all the code that's specific to this particular application.
-
-app/assets
-  Contains subdirectories for images, stylesheets, and JavaScript files.
-
-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. Models descend from
-  ActiveRecord::Base by default.
-
-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 by default.
-
-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 generators 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. 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 rails generate
-  command, 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.