cdn_sumo_sprockets_rails2 0.0.1

data/.gitignore

@@ -0,0 +1,5 @@
+*.gem
+.bundle
+Gemfile.lock
+pkg/*
+test/dummy/log/*

data/Gemfile

@@ -0,0 +1,10 @@
+source "http://rubygems.org"
+
+# Specify your gem's dependencies in sprockets-rails2.gemspec
+gemspec
+gem 'rake'
+
+group :test do
+  gem 'minitest'
+  gem 'rails', '2.3.16'
+end

data/Rakefile

@@ -0,0 +1,11 @@
+require 'bundler'
+Bundler::GemHelper.install_tasks
+require 'rake/testtask'
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << 'test'
+  t.test_files = FileList['test/**/*_test.rb']
+  t.verbose = true
+end
+
+task :default => [:test]

data/cdn_sumo_sprockets_rails2.gemspec

@@ -0,0 +1,23 @@
+# -*- encoding: utf-8 -*-
+$:.push File.expand_path("../lib", __FILE__)
+require "cdn_sumo_sprockets_rails2/rails2/version"
+
+Gem::Specification.new do |s|
+  s.name        = "cdn_sumo_sprockets_rails2"
+  s.version     = CdnSumoSprockets::Rails2::VERSION
+  s.platform    = Gem::Platform::RUBY
+  s.authors     = ["Richard Schneeman"]
+  s.email       = ["richard.schneeman@gmail.com"]
+  s.homepage    = ""
+  s.summary     = %q{Provides asset pipeline and CDN Sumo functionality to Rails 2.3}
+  s.description = %q{The gem allows Rails 2.3 apps to use the
+                     same asset pipeline functionality introduced in Rails 3.1.
+                     It does this by integrating the Sprockets gem into a Rails
+                     2.3 app, and automatically applying configuration for CDN Sumo }
+
+  s.files         = `git ls-files`.split("\n")
+  s.test_files    = `git ls-files -- {test,spec,features}/*`.split("\n")
+  s.executables   = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
+  s.require_paths = ["lib"]
+  s.add_dependency("sprockets", '~> 2.8.2')
+end

data/lib/cdn_sumo_sprockets_rails2.rb

@@ -0,0 +1,16 @@
+require 'cdn_sumo_sprockets_rails2/rails2/asset_helpers'
+require 'cdn_sumo_sprockets_rails2/rails2/asset_pipeline'
+require 'cdn_sumo_sprockets_rails2/rails2/middleware'
+
+
+if defined?(ActionController)
+  ActionController::Dispatcher.middleware.use Sprockets::Rails2::Middleware
+
+  ActionController::Base.asset_host = Proc.new { |source, request|
+    if host = ENV['CDN_SUMO_URL']
+      "#{request.protocol}#{host}"
+    else
+      "#{request.protocol}#{request.host_with_port}"
+    end
+  }
+end

data/lib/cdn_sumo_sprockets_rails2/rails2/asset_helpers.rb

@@ -0,0 +1,14 @@
+module ActionView
+  module Helpers
+    def rewrite_asset_path(source)
+      source = source.gsub(/^\//, "")  # remove the leading /
+      source = source.gsub(/^images\/|^stylesheets\/|^javascripts\//, "") # remove leading images/ stylesheets/ or javascripts/
+      if asset = Rails.asset_pipeline.find_asset(source)
+        File.join("/assets/", asset.digest_path)
+      else
+        "/#{source}"
+      end
+    end
+    alias :asset_path :rewrite_asset_path
+  end
+end

data/lib/cdn_sumo_sprockets_rails2/rails2/asset_pipeline.rb

@@ -0,0 +1,21 @@
+require 'sprockets'
+
+module Rails
+  class << self
+    def asset_pipeline
+      @asset_pipeline ||= initialize_pipeline
+    end
+
+    def initialize_pipeline
+      sprockets = Sprockets::Environment.new
+      sprockets.append_path(File.join(Rails.root, "app/assets/javascripts"))
+      sprockets.append_path(File.join(Rails.root, "app/assets/stylesheets"))
+      sprockets.append_path(File.join(Rails.root, "app/assets/images"))
+
+      sprockets.context_class.instance_eval do
+        include ActionView::Helpers
+      end
+      sprockets
+    end
+  end
+end

data/lib/cdn_sumo_sprockets_rails2/rails2/middleware.rb

@@ -0,0 +1,21 @@
+
+module Sprockets
+  module Rails2
+    class Middleware
+      PREFIX = %r{/assets}
+
+      def initialize(app)
+        @app = app
+      end
+
+      def call(env)
+        if env['PATH_INFO'] =~ PREFIX
+          env['PATH_INFO']  = env['PATH_INFO'].sub(PREFIX, "")
+          Rails.asset_pipeline.call(env)
+        else
+          @app.call(env)
+        end
+      end
+    end
+  end
+end

data/lib/cdn_sumo_sprockets_rails2/rails2/version.rb

@@ -0,0 +1,5 @@
+module CdnSumoSprockets
+  module Rails2
+    VERSION = "0.0.1"
+  end
+end

data/lib/cdn_sumo_sprockets_rails2/tasks.rb

@@ -0,0 +1 @@
+load "cdn_sumo_sprockets_rails2/tasks/assets.rake"

data/lib/cdn_sumo_sprockets_rails2/tasks/assets.rake

@@ -0,0 +1,75 @@
+# lib/tasks/assets.rake
+
+require "fileutils"
+require 'pathname'
+require 'sprockets'
+
+namespace :assets do
+  def ruby_rake_task(task, fork = true)
+    env    = ENV['RAILS_ENV'] || 'production'
+    groups = ENV['RAILS_GROUPS'] || 'assets'
+    args   = [$0, task, "RAILS_ENV=" + env, "RAILS_GROUPS=" + groups]
+    args << "--trace" if Rake.application.options.trace
+    if $0 =~ /rake\.bat\Z/i
+      Kernel.exec $0, *args
+    else
+      fork ? ruby(*args) : Kernel.exec(FileUtils::RUBY, *args)
+    end
+  end
+
+  # We are currently running with no explicit bundler group
+  # and/or no explicit environment - we have to reinvoke rake to
+  # execute this task.
+  def invoke_or_reboot_rake_task(task)
+    if ENV['RAILS_GROUPS'].to_s.empty? || ENV['RAILS_ENV'].to_s.empty?
+      ruby_rake_task task
+    else
+      Rake::Task[task].invoke
+    end
+  end
+
+  desc "Compile all the assets named in config.assets.precompile"
+  task :precompile do
+    invoke_or_reboot_rake_task "assets:precompile:all"
+  end
+
+  namespace :precompile do
+    def internal_precompile(digest = nil)
+
+      # Ensure that action view is loaded and the appropriate
+      # sprockets hooks get executed
+      _ = ActionView::Base
+
+      manifest = Sprockets::Manifest.new(Rails.asset_pipeline , Rails.root.join("public", "assets", "manifest.json"))
+      manifest.compile
+    end
+
+    task :all do
+      Rake::Task["assets:precompile:primary"].invoke
+    end
+
+    task :primary => ["assets:environment", "tmp:cache:clear"] do
+      internal_precompile
+    end
+
+    task :nondigest => ["assets:environment", "tmp:cache:clear"] do
+      internal_precompile(false)
+    end
+  end
+
+  desc "Remove compiled assets"
+  task :clean do
+    invoke_or_reboot_rake_task "assets:clean:all"
+  end
+
+  namespace :clean do
+    task :all => ["assets:environment", "tmp:cache:clear"] do
+      public_asset_path = Pathname.new(Rails.public_path).join("assets")
+      rm_rf public_asset_path, :secure => true
+    end
+  end
+
+  task :environment do
+    Rake::Task["environment"].invoke
+  end
+end

data/test/dummy/.gitignore

@@ -0,0 +1 @@
+tmp/*

data/test/dummy/README

@@ -0,0 +1,243 @@
+== 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.