environmentalist 0.1.0

data/History.txt

@@ -0,0 +1,4 @@
+=== v0.1.0
+2008-08-04
+
+* Initial Release: environmentalize executable will make environments first-class citizens in your rails app!

data/Manifest.txt

@@ -0,0 +1,58 @@
+History.txt
+Manifest.txt
+README.txt
+Rakefile
+bin/environmentalize
+environmentalist.gemspec
+lib/conf/postboot.rb
+lib/environmentalist.rb
+lib/environmentalist/version.rb
+test/rails210/README
+test/rails210/Rakefile
+test/rails210/app/controllers/application.rb
+test/rails210/app/helpers/application_helper.rb
+test/rails210/config/boot.rb
+test/rails210/config/database.yml
+test/rails210/config/environment.rb
+test/rails210/config/environments/development.rb
+test/rails210/config/environments/production.rb
+test/rails210/config/environments/test.rb
+test/rails210/config/initializers/inflections.rb
+test/rails210/config/initializers/mime_types.rb
+test/rails210/config/initializers/new_rails_defaults.rb
+test/rails210/config/routes.rb
+test/rails210/doc/README_FOR_APP
+test/rails210/log/development.log
+test/rails210/log/production.log
+test/rails210/log/server.log
+test/rails210/log/test.log
+test/rails210/public/404.html
+test/rails210/public/422.html
+test/rails210/public/500.html
+test/rails210/public/dispatch.cgi
+test/rails210/public/dispatch.fcgi
+test/rails210/public/dispatch.rb
+test/rails210/public/favicon.ico
+test/rails210/public/images/rails.png
+test/rails210/public/index.html
+test/rails210/public/javascripts/application.js
+test/rails210/public/javascripts/controls.js
+test/rails210/public/javascripts/dragdrop.js
+test/rails210/public/javascripts/effects.js
+test/rails210/public/javascripts/prototype.js
+test/rails210/public/robots.txt
+test/rails210/script/about
+test/rails210/script/console
+test/rails210/script/dbconsole
+test/rails210/script/destroy
+test/rails210/script/generate
+test/rails210/script/performance/benchmarker
+test/rails210/script/performance/profiler
+test/rails210/script/performance/request
+test/rails210/script/plugin
+test/rails210/script/process/inspector
+test/rails210/script/process/reaper
+test/rails210/script/process/spawner
+test/rails210/script/runner
+test/rails210/script/server
+test/rails_version_test.rb

data/README.txt

@@ -0,0 +1,43 @@
+= environmentalist
+
+* http://github.com/jtrupiano/environmentalist/tree/master
+
+== DESCRIPTION:
+Provides an executable that converts a rails app's config structure.  The basic idea is that environments themselves are now first-class citizens, allowing you to create several environments (e.g. staging, prodtest, demo, etc.) in a clean, organized fashion.  Each environment is given its own folder where it can store its own set of configuration files (think mongrel configs, apache configs, etc.) without polluting the top-leve config/ directory.
+
+== SYNOPSIS:
+
+  FIX (code sample of usage)
+
+== REQUIREMENTS:
+
+* none, but it's really only useful with a rails app
+
+== INSTALL:
+
+* sudo gem install environmentalist
+
+== LICENSE:
+
+(The MIT License)
+
+Copyright (c) 2008 FIX
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+'Software'), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/Rakefile

@@ -0,0 +1,32 @@
+# -*- ruby -*-
+
+require 'rubygems'
+require 'hoe'
+require './lib/environmentalist.rb'
+require "./lib/environmentalist/version"
+
+PKG_NAME      = "environmentalist"
+PKG_BUILD     = ENV['PKG_BUILD'] ? '.' + ENV['PKG_BUILD'] : ''
+version = Environmentalist::Version::STRING.dup
+if ENV['SNAPSHOT'].to_i == 1
+  version << "." << Time.now.utc.strftime("%Y%m%d%H%M%S")
+end
+PKG_VERSION   = version
+PKG_FILE_NAME = "#{PKG_NAME}-#{PKG_VERSION}"
+
+Hoe.new(PKG_NAME, PKG_VERSION) do |p|
+  p.rubyforge_name = 'johntrupiano' # if different than lowercase project name
+  p.developer('John Trupiano', 'jtrupiano@gmail.com')
+  p.name = PKG_NAME
+  p.version = PKG_VERSION
+  p.author = "John Trupiano"
+  p.email = "jtrupiano@gmail.com"
+  p.description = %q(Provides an executable that converts a rails app's config structure.  The basic idea is that environments themselves are now first-class citizens, allowing you to create several environments (e.g. staging, prodtest, demo, etc.) in a clean, organized fashion.  Each environment is given its own folder where it can store its own set of configuration files (think mongrel configs, apache configs, etc.) without polluting the top-leve config/ direcotory.)
+  p.summary = p.description # More details later??
+  p.remote_rdoc_dir = PKG_NAME # Release to /PKG_NAME
+  #  p.changes = p.paragraphs_of('CHANGELOG', 0..1).join("\n\n")
+  p.need_zip = true
+  p.need_tar = false
+end
+
+# vim: syntax=Ruby

data/bin/environmentalize

@@ -0,0 +1,84 @@
+#!/usr/bin/env ruby
+# environmentalize
+# Author: John Trupiano
+
+require 'fileutils'
+include FileUtils
+
+require 'yaml'
+
+rails_root = ARGV[0] || '.'
+puts "rails_root: #{rails_root}"
+config_base = File.join(rails_root, 'config')
+old_env_dir = File.join(config_base, 'environments')
+
+%w(demo development production staging test).each do |env|
+  dir = File.join(config_base, env)
+	if !File.directory?(dir)
+		puts "mkdir -p #{dir}"
+		mkdir_p dir
+	end
+	old_env_file = File.join(old_env_dir, "#{env}.rb")
+	if File.exists?(old_env_file)
+	  new_env_file = File.join(dir, "environment.rb")
+	  puts "mv #{old_env_file} #{new_env_file}"
+	  mv(old_env_file, new_env_file)
+	end
+end
+
+# Copy production for these guys if it wasn't already found
+%w(demo staging).each do |env|
+  new_env_file = File.join(config_base, env, "environment.rb")
+  prod_env_file = File.join(config_base, "production", "environment.rb")
+  if !File.exists?(new_env_file)
+    puts "cp #{prod_env_file} #{new_env_file}"
+    cp(prod_env_file, new_env_file)
+  end
+end
+
+#cp $GEM_HOME/environmentalist-0.1.0/conf/postboot.rb config/postboot.rb
+postboot = File.join(config_base, "postboot.rb")
+if !File.exists?(postboot)
+  gem_postboot = File.dirname(__FILE__) + '/../lib/conf/postboot.rb'
+  puts "cp #{gem_postboot} #{postboot}"
+  cp(gem_postboot, postboot)
+end
+
+main_env_file = File.join(config_base, "environment.rb")
+env_contents = File.open(main_env_file).read
+if !env_contents.include?("require File.join(File.dirname(__FILE__), 'postboot')")
+  
+  contents = <<-CONTENTS
+# Load postboot file to change Rails paths
+require File.join(File.dirname(__FILE__), 'postboot')
+
+Rails::Initializer.run do |config|
+  CONTENTS
+  
+  env_contents.sub!("Rails::Initializer.run do |config|", contents)
+  File.open(main_env_file, 'w') {|f| f.write(env_contents) }
+end
+
+if File.directory?(old_env_dir)
+  puts "Removing #{old_env_dir}"
+  rm_rf(old_env_dir)
+end
+
+# Handle database.yml now
+old_db_yml = File.join(config_base, 'database.yml')
+if File.exists?(old_db_yml)
+  y = YAML.load_file(old_db_yml)
+  %w(demo development production staging test).each do |env|
+    new_db_yml = File.join(config_base, env, 'database.yml')
+    if !File.exists?(new_db_yml)
+      if !y[env].nil?
+        puts "Writing #{new_db_yml}"
+        # remove all other keys
+        y_dup = y.reject {|key, value| key != env}
+        File.open(new_db_yml, 'w') {|f| f. write(y_dup.to_yaml) }
+      end
+    end
+  end
+  puts "Removing #{old_db_yml}"
+  rm_f(old_db_yml)
+end

data/environmentalist.gemspec

@@ -0,0 +1,35 @@
+Gem::Specification.new do |s|
+  s.name = %q{environmentalist}
+  s.version = "0.1.0"
+
+  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
+  s.authors = ["John Trupiano"]
+  s.date = %q{2008-09-12}
+  s.default_executable = %q{environmentalize}
+  s.description = %q{Provides an executable that converts a rails app's config structure.  The basic idea is that environments themselves are now first-class citizens, allowing you to create several environments (e.g. staging, prodtest, demo, etc.) in a clean, organized fashion.  Each environment is given its own folder where it can store its own set of configuration files (think mongrel configs, apache configs, etc.) without polluting the top-leve config/ direcotory.}
+  s.email = %q{jtrupiano@gmail.com}
+  s.executables = ["environmentalize"]
+  s.extra_rdoc_files = ["History.txt", "Manifest.txt", "README.txt"]
+  s.files = ["History.txt", "Manifest.txt", "README.txt", "Rakefile", "bin/environmentalize", "environmentalist.gemspec", "lib/conf/postboot.rb", "lib/environmentalist.rb", "lib/environmentalist/version.rb", "test/rails210/README", "test/rails210/Rakefile", "test/rails210/app/controllers/application.rb", "test/rails210/app/helpers/application_helper.rb", "test/rails210/config/boot.rb", "test/rails210/config/database.yml", "test/rails210/config/environment.rb", "test/rails210/config/environments/development.rb", "test/rails210/config/environments/production.rb", "test/rails210/config/environments/test.rb", "test/rails210/config/initializers/inflections.rb", "test/rails210/config/initializers/mime_types.rb", "test/rails210/config/initializers/new_rails_defaults.rb", "test/rails210/config/routes.rb", "test/rails210/doc/README_FOR_APP", "test/rails210/log/development.log", "test/rails210/log/production.log", "test/rails210/log/server.log", "test/rails210/log/test.log", "test/rails210/public/404.html", "test/rails210/public/422.html", "test/rails210/public/500.html", "test/rails210/public/dispatch.cgi", "test/rails210/public/dispatch.fcgi", "test/rails210/public/dispatch.rb", "test/rails210/public/favicon.ico", "test/rails210/public/images/rails.png", "test/rails210/public/index.html", "test/rails210/public/javascripts/application.js", "test/rails210/public/javascripts/controls.js", "test/rails210/public/javascripts/dragdrop.js", "test/rails210/public/javascripts/effects.js", "test/rails210/public/javascripts/prototype.js", "test/rails210/public/robots.txt", "test/rails210/script/about", "test/rails210/script/console", "test/rails210/script/dbconsole", "test/rails210/script/destroy", "test/rails210/script/generate", "test/rails210/script/performance/benchmarker", "test/rails210/script/performance/profiler", "test/rails210/script/performance/request", "test/rails210/script/plugin", "test/rails210/script/process/inspector", "test/rails210/script/process/reaper", "test/rails210/script/process/spawner", "test/rails210/script/runner", "test/rails210/script/server", "test/rails_version_test.rb", "test/rails210/test/test_helper.rb", "test/rails210test/test/test_helper.rb"]
+  s.has_rdoc = true
+  s.homepage = %q{http://github.com/jtrupiano/environmentalist/tree/master}
+  s.rdoc_options = ["--main", "README.txt"]
+  s.require_paths = ["lib"]
+  s.rubyforge_project = %q{johntrupiano}
+  s.rubygems_version = %q{1.2.0}
+  s.summary = %q{Provides an executable that converts a rails app's config structure.  The basic idea is that environments themselves are now first-class citizens, allowing you to create several environments (e.g. staging, prodtest, demo, etc.) in a clean, organized fashion.  Each environment is given its own folder where it can store its own set of configuration files (think mongrel configs, apache configs, etc.) without polluting the top-leve config/ direcotory.}
+  s.test_files = ["test/rails_version_test.rb"]
+
+  if s.respond_to? :specification_version then
+    current_version = Gem::Specification::CURRENT_SPECIFICATION_VERSION
+    s.specification_version = 2
+
+    if current_version >= 3 then
+      s.add_development_dependency(%q<hoe>, [">= 1.7.0"])
+    else
+      s.add_dependency(%q<hoe>, [">= 1.7.0"])
+    end
+  else
+    s.add_dependency(%q<hoe>, [">= 1.7.0"])
+  end
+end

data/lib/conf/postboot.rb

@@ -0,0 +1,38 @@
+# Be sure to restart your server when you modify this file.
+
+rails_env = ENV['RAILS_ENV'] || 'development'
+
+env_dir  = File.join(RAILS_ROOT, 'config', rails_env)
+db_file  = File.join(env_dir, 'database.yml')
+env_file = File.join(env_dir, 'environment.rb')
+
+unless File.exists?(env_dir)
+  puts "#{env_dir} environment directory cannot be found."
+  exit(1)
+end
+
+unless File.exists?(db_file)
+	puts "#{db_file} is missing.  You cannot continue without this."
+	exit(1) # exit with an error code
+end
+
+unless File.exists?(env_file)
+  puts "#{env_file} environment file is missing." 
+  exit(1)
+end
+
+# Now, let's open up Rails and tell it to find our environment files elsewhere.
+module Rails
+  class Configuration
+    
+    def database_configuration_file
+      File.join(root_path, 'config', environment, 'database.yml')
+    end
+    
+    # The path to the current environment's file (development.rb, etc.). By
+    # default the file is at <tt>config/environments/#{environment}.rb</tt>.
+    def environment_path
+      "#{root_path}/config/#{environment}/environment.rb"
+    end
+  end
+end

data/lib/environmentalist.rb

@@ -0,0 +1 @@
+gem 'rails', '>= 2.0.2'  # ensure rails is loaded

data/lib/environmentalist/version.rb

@@ -0,0 +1,20 @@
+module Environmentalist
+  module Version #:nodoc:
+    # A method for comparing versions of required modules. It expects two
+    # arrays of integers as parameters, the first being the minimum version
+    # required, and the second being the actual version available. It returns
+    # true if the actual version is at least equal to the required version.
+    def self.check(required, actual) #:nodoc:
+      required = required.map { |v| "%06d" % v }.join(".")
+      actual   = actual.map { |v| "%06d" % v }.join(".")
+      return actual >= required
+    end
+
+    MAJOR = 0
+    MINOR = 1
+    TINY  = 0
+
+    STRING = [MAJOR, MINOR, TINY].join(".")
+  end
+end
+

data/test/rails210/README

@@ -0,0 +1,256 @@
+== 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 and lighttpd if they are installed, otherwise
+Rails will use 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
+
+
+== Apache .htaccess example
+
+# 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.