environmentalist 0.1.0

data/test/rails210/public/robots.txt

@@ -0,0 +1,5 @@
+# See http://www.robotstxt.org/wc/norobots.html for documentation on how to use the robots.txt file
+#
+# To ban all spiders from the entire site uncomment the next two lines:
+# User-Agent: *
+# Disallow: /

data/test/rails210/script/about

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../config/boot'
+require 'commands/about'

data/test/rails210/script/console

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../config/boot'
+require 'commands/console'

data/test/rails210/script/dbconsole

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../config/boot'
+require 'commands/dbconsole'

data/test/rails210/script/destroy

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../config/boot'
+require 'commands/destroy'

data/test/rails210/script/generate

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../config/boot'
+require 'commands/generate'

data/test/rails210/script/performance/benchmarker

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../../config/boot'
+require 'commands/performance/benchmarker'

data/test/rails210/script/performance/profiler

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../../config/boot'
+require 'commands/performance/profiler'

data/test/rails210/script/performance/request

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../../config/boot'
+require 'commands/performance/request'

data/test/rails210/script/plugin

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../config/boot'
+require 'commands/plugin'

data/test/rails210/script/process/inspector

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../../config/boot'
+require 'commands/process/inspector'

data/test/rails210/script/process/reaper

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../../config/boot'
+require 'commands/process/reaper'

data/test/rails210/script/process/spawner

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../../config/boot'
+require 'commands/process/spawner'

data/test/rails210/script/runner

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../config/boot'
+require 'commands/runner'

data/test/rails210/script/server

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../config/boot'
+require 'commands/server'

data/test/rails210/test/test_helper.rb

@@ -0,0 +1,38 @@
+ENV["RAILS_ENV"] = "test"
+require File.expand_path(File.dirname(__FILE__) + "/../config/environment")
+require 'test_help'
+
+class Test::Unit::TestCase
+  # Transactional fixtures accelerate your tests by wrapping each test method
+  # in a transaction that's rolled back on completion.  This ensures that the
+  # test database remains unchanged so your fixtures don't have to be reloaded
+  # between every test method.  Fewer database queries means faster tests.
+  #
+  # Read Mike Clark's excellent walkthrough at
+  #   http://clarkware.com/cgi/blosxom/2005/10/24#Rails10FastTesting
+  #
+  # Every Active Record database supports transactions except MyISAM tables
+  # in MySQL.  Turn off transactional fixtures in this case; however, if you
+  # don't care one way or the other, switching from MyISAM to InnoDB tables
+  # is recommended.
+  #
+  # The only drawback to using transactional fixtures is when you actually 
+  # need to test transactions.  Since your test is bracketed by a transaction,
+  # any transactions started in your code will be automatically rolled back.
+  self.use_transactional_fixtures = true
+
+  # Instantiated fixtures are slow, but give you @david where otherwise you
+  # would need people(:david).  If you don't want to migrate your existing
+  # test cases which use the @david style and don't mind the speed hit (each
+  # instantiated fixtures translates to a database query per test method),
+  # then set this back to true.
+  self.use_instantiated_fixtures  = false
+
+  # Setup all fixtures in test/fixtures/*.(yml|csv) for all tests in alphabetical order.
+  #
+  # Note: You'll currently still have to declare fixtures explicitly in integration tests
+  # -- they do not yet inherit this setting
+  fixtures :all
+
+  # Add more helper methods to be used by all tests here...
+end

data/test/rails210test/test/test_helper.rb

@@ -0,0 +1,38 @@
+ENV["RAILS_ENV"] = "test"
+require File.expand_path(File.dirname(__FILE__) + "/../config/environment")
+require 'test_help'
+
+class Test::Unit::TestCase
+  # Transactional fixtures accelerate your tests by wrapping each test method
+  # in a transaction that's rolled back on completion.  This ensures that the
+  # test database remains unchanged so your fixtures don't have to be reloaded
+  # between every test method.  Fewer database queries means faster tests.
+  #
+  # Read Mike Clark's excellent walkthrough at
+  #   http://clarkware.com/cgi/blosxom/2005/10/24#Rails10FastTesting
+  #
+  # Every Active Record database supports transactions except MyISAM tables
+  # in MySQL.  Turn off transactional fixtures in this case; however, if you
+  # don't care one way or the other, switching from MyISAM to InnoDB tables
+  # is recommended.
+  #
+  # The only drawback to using transactional fixtures is when you actually 
+  # need to test transactions.  Since your test is bracketed by a transaction,
+  # any transactions started in your code will be automatically rolled back.
+  self.use_transactional_fixtures = true
+
+  # Instantiated fixtures are slow, but give you @david where otherwise you
+  # would need people(:david).  If you don't want to migrate your existing
+  # test cases which use the @david style and don't mind the speed hit (each
+  # instantiated fixtures translates to a database query per test method),
+  # then set this back to true.
+  self.use_instantiated_fixtures  = false
+
+  # Setup all fixtures in test/fixtures/*.(yml|csv) for all tests in alphabetical order.
+  #
+  # Note: You'll currently still have to declare fixtures explicitly in integration tests
+  # -- they do not yet inherit this setting
+  fixtures :all
+
+  # Add more helper methods to be used by all tests here...
+end

data/test/rails_version_test.rb

@@ -0,0 +1,38 @@
+require 'test/unit'
+require 'fileutils'
+require 'yaml'
+
+class RailsVersionTest < Test::Unit::TestCase
+  include FileUtils
+  
+  def test_rails_two_one_zero
+    # Clean up an old run if necessary
+    rm_rf('rails210test')
+    
+    cp_r('rails210', 'rails210test')
+    system("environmentalize rails210test")
+    
+    config_root = File.join('rails210test', 'config')
+    
+    assert File.exists?(File.join(config_root, 'postboot.rb'))
+    
+    env_rb = File.open(File.join(config_root, 'environment.rb')).read
+    assert env_rb.include?("require File.join(File.dirname(__FILE__), 'postboot')")
+    
+    %w(development test demo staging production).each do |env|
+      assert File.directory?(File.join(config_root, env))
+    end
+    
+    %w(development test production).each do |env|
+      %w(database.yml environment.rb).each do |f|
+         assert File.exists?(File.join(config_root, env, f))
+       end
+       puts "Testing #{env}"
+       y = YAML.load_file(File.join(config_root, env, 'database.yml'))
+       assert_equal 1, y.keys.size
+       assert_equal env, y.keys.first
+    end
+#  ensure
+#    rm_rf('rails210test')
+  end
+end

metadata

@@ -0,0 +1,124 @@
+--- !ruby/object:Gem::Specification 
+name: environmentalist
+version: !ruby/object:Gem::Version 
+  version: 0.1.0
+platform: ruby
+authors: 
+- John Trupiano
+autorequire: 
+bindir: bin
+cert_chain: []
+
+date: 2008-09-12 00:00:00 -04:00
+default_executable: 
+dependencies: 
+- !ruby/object:Gem::Dependency 
+  name: hoe
+  type: :development
+  version_requirement: 
+  version_requirements: !ruby/object:Gem::Requirement 
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        version: 1.7.0
+    version: 
+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/ direcotory.
+email: jtrupiano@gmail.com
+executables: 
+- environmentalize
+extensions: []
+
+extra_rdoc_files: 
+- History.txt
+- Manifest.txt
+- README.txt
+- test/rails210/public/robots.txt
+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
+has_rdoc: true
+homepage: http://github.com/jtrupiano/environmentalist/tree/master
+post_install_message: 
+rdoc_options: 
+- --main
+- README.txt
+require_paths: 
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
+  version: 
+required_rubygems_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
+  version: 
+requirements: []
+
+rubyforge_project: johntrupiano
+rubygems_version: 1.2.0
+signing_key: 
+specification_version: 2
+summary: 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.
+test_files: 
+- test/rails210/test/test_helper.rb
+- test/rails210test/test/test_helper.rb