environmentalist 0.1.0 → 0.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (64) hide show
  1. data/History.txt +11 -0
  2. data/{README.txt → LICENSE} +0 -21
  3. data/README.textile +22 -0
  4. data/Rakefile +19 -29
  5. data/VERSION.yml +4 -0
  6. data/bin/environmentalize +7 -1
  7. data/lib/conf/postboot.rb +3 -14
  8. data/lib/conf/preinitializer.rb +20 -0
  9. data/test/rails210test/README +256 -0
  10. data/test/rails210test/Rakefile +10 -0
  11. data/test/rails210test/app/controllers/application.rb +15 -0
  12. data/test/rails210test/app/helpers/application_helper.rb +3 -0
  13. data/test/rails210test/config/boot.rb +109 -0
  14. data/test/rails210test/config/demo/environment.rb +22 -0
  15. data/test/rails210test/config/development/database.yml +5 -0
  16. data/test/rails210test/config/development/environment.rb +17 -0
  17. data/test/rails210test/config/environment.rb +71 -0
  18. data/test/rails210test/config/initializers/inflections.rb +10 -0
  19. data/test/rails210test/config/initializers/mime_types.rb +5 -0
  20. data/test/rails210test/config/initializers/new_rails_defaults.rb +15 -0
  21. data/test/rails210test/config/postboot.rb +38 -0
  22. data/test/rails210test/config/production/database.yml +5 -0
  23. data/test/rails210test/config/production/environment.rb +22 -0
  24. data/test/rails210test/config/routes.rb +41 -0
  25. data/test/rails210test/config/staging/environment.rb +22 -0
  26. data/test/rails210test/config/test/database.yml +5 -0
  27. data/test/rails210test/config/test/environment.rb +22 -0
  28. data/test/rails210test/doc/README_FOR_APP +2 -0
  29. data/test/rails210test/log/development.log +0 -0
  30. data/test/rails210test/log/production.log +0 -0
  31. data/test/rails210test/log/server.log +0 -0
  32. data/test/rails210test/log/test.log +0 -0
  33. data/test/rails210test/public/404.html +30 -0
  34. data/test/rails210test/public/422.html +30 -0
  35. data/test/rails210test/public/500.html +30 -0
  36. data/test/rails210test/public/dispatch.cgi +10 -0
  37. data/test/rails210test/public/dispatch.fcgi +24 -0
  38. data/test/rails210test/public/dispatch.rb +10 -0
  39. data/test/rails210test/public/favicon.ico +0 -0
  40. data/test/rails210test/public/images/rails.png +0 -0
  41. data/test/rails210test/public/index.html +274 -0
  42. data/test/rails210test/public/javascripts/application.js +2 -0
  43. data/test/rails210test/public/javascripts/controls.js +963 -0
  44. data/test/rails210test/public/javascripts/dragdrop.js +972 -0
  45. data/test/rails210test/public/javascripts/effects.js +1120 -0
  46. data/test/rails210test/public/javascripts/prototype.js +4225 -0
  47. data/test/rails210test/public/robots.txt +5 -0
  48. data/test/rails210test/script/about +3 -0
  49. data/test/rails210test/script/console +3 -0
  50. data/test/rails210test/script/dbconsole +3 -0
  51. data/test/rails210test/script/destroy +3 -0
  52. data/test/rails210test/script/generate +3 -0
  53. data/test/rails210test/script/performance/benchmarker +3 -0
  54. data/test/rails210test/script/performance/profiler +3 -0
  55. data/test/rails210test/script/performance/request +3 -0
  56. data/test/rails210test/script/plugin +3 -0
  57. data/test/rails210test/script/process/inspector +3 -0
  58. data/test/rails210test/script/process/reaper +3 -0
  59. data/test/rails210test/script/process/spawner +3 -0
  60. data/test/rails210test/script/runner +3 -0
  61. data/test/rails210test/script/server +3 -0
  62. metadata +153 -36
  63. data/Manifest.txt +0 -58
  64. data/environmentalist.gemspec +0 -35
data/History.txt CHANGED
@@ -1,3 +1,14 @@
1
+ === v0.2.1
2
+ 2009-03-06
3
+
4
+ * Add automatic gem install + activation (bug fix for GemInstaller pending) added to preinitializer.rb
5
+
6
+ === v0.2.0
7
+ 2009-03-02
8
+
9
+ * Added preinitializer.rb to the set of the generated files for you. It auto-loads gem dependencies as specified in geminstaller.yml files that can be distributed across your environment directories.
10
+ * Moved gem onto jeweler (with the temporary loss of rubyforge support --- rubyforge integration has been achieved in a fork of the jeweler repo, so we should have it back once it's merged back into the main line.)
11
+
1
12
  === v0.1.0
2
13
  2008-08-04
3
14
 
@@ -1,24 +1,3 @@
1
- = environmentalist
2
-
3
- * http://github.com/jtrupiano/environmentalist/tree/master
4
-
5
- == DESCRIPTION:
6
- 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.
7
-
8
- == SYNOPSIS:
9
-
10
- FIX (code sample of usage)
11
-
12
- == REQUIREMENTS:
13
-
14
- * none, but it's really only useful with a rails app
15
-
16
- == INSTALL:
17
-
18
- * sudo gem install environmentalist
19
-
20
- == LICENSE:
21
-
22
1
  (The MIT License)
23
2
 
24
3
  Copyright (c) 2008 FIX
data/README.textile ADDED
@@ -0,0 +1,22 @@
1
+ h1. environmentalist
2
+
3
+ * http://github.com/jtrupiano/environmentalist/tree/master
4
+
5
+ h2. DESCRIPTION
6
+
7
+ 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.
8
+
9
+ h2. REQUIREMENTS
10
+
11
+ * none, but it's really only useful with a rails app
12
+
13
+ h2. INSTALL
14
+
15
+ sudo gem install environmentalist
16
+
17
+ h2. USAGE
18
+
19
+ This gem is intended to be a "one-time consumption." You use it once to alter/convert the structure of your rails app (works best with a newly-generated app). It should <b>not</b> be included as a gem dependency for your project.
20
+
21
+ environmentalize /path/to/rails/root
22
+
data/Rakefile CHANGED
@@ -1,32 +1,22 @@
1
- # -*- ruby -*-
1
+ require 'rake'
2
+ require 'rake/testtask'
3
+ require 'rake/rdoctask'
2
4
 
3
- require 'rubygems'
4
- require 'hoe'
5
- require './lib/environmentalist.rb'
6
- require "./lib/environmentalist/version"
7
-
8
- PKG_NAME = "environmentalist"
9
- PKG_BUILD = ENV['PKG_BUILD'] ? '.' + ENV['PKG_BUILD'] : ''
10
- version = Environmentalist::Version::STRING.dup
11
- if ENV['SNAPSHOT'].to_i == 1
12
- version << "." << Time.now.utc.strftime("%Y%m%d%H%M%S")
13
- end
14
- PKG_VERSION = version
15
- PKG_FILE_NAME = "#{PKG_NAME}-#{PKG_VERSION}"
16
-
17
- Hoe.new(PKG_NAME, PKG_VERSION) do |p|
18
- p.rubyforge_name = 'johntrupiano' # if different than lowercase project name
19
- p.developer('John Trupiano', 'jtrupiano@gmail.com')
20
- p.name = PKG_NAME
21
- p.version = PKG_VERSION
22
- p.author = "John Trupiano"
23
- p.email = "jtrupiano@gmail.com"
24
- 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.)
25
- p.summary = p.description # More details later??
26
- p.remote_rdoc_dir = PKG_NAME # Release to /PKG_NAME
27
- # p.changes = p.paragraphs_of('CHANGELOG', 0..1).join("\n\n")
28
- p.need_zip = true
29
- p.need_tar = false
5
+ begin
6
+ require 'jeweler'
7
+ Jeweler::Tasks.new do |s|
8
+ s.name = "environmentalist"
9
+ s.rubyforge_project = 'johntrupiano' # if different than lowercase project name
10
+ 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/ directory.)
11
+ s.summary = s.description # More details later??
12
+ s.email = "jtrupiano@gmail.com"
13
+ s.homepage = "http://github.com/jtrupiano/environmentalist"
14
+ s.authors = ["John Trupiano"]
15
+ s.executables = "environmentalize"
16
+ s.files = FileList["[A-Z]*", "{bin,lib,test}/**/*"]
17
+ #s.add_dependency 'schacon-git'
18
+ end
19
+ rescue LoadError
20
+ puts "Jeweler, or one of its dependencies, is not available. Install it with: sudo gem install technicalpickles-jeweler -s http://gems.github.com"
30
21
  end
31
22
 
32
- # vim: syntax=Ruby
data/VERSION.yml ADDED
@@ -0,0 +1,4 @@
1
+ ---
2
+ :patch: 1
3
+ :major: 0
4
+ :minor: 2
data/bin/environmentalize CHANGED
@@ -36,7 +36,6 @@ end
36
36
  end
37
37
  end
38
38
 
39
- #cp $GEM_HOME/environmentalist-0.1.0/conf/postboot.rb config/postboot.rb
40
39
  postboot = File.join(config_base, "postboot.rb")
41
40
  if !File.exists?(postboot)
42
41
  gem_postboot = File.dirname(__FILE__) + '/../lib/conf/postboot.rb'
@@ -44,6 +43,13 @@ if !File.exists?(postboot)
44
43
  cp(gem_postboot, postboot)
45
44
  end
46
45
 
46
+ preinitializer = File.join(config_base, "preinitializer.rb")
47
+ if !File.exists?(preinitializer)
48
+ gem_preinitializer = File.join(File.dirname(__FILE__), '..', 'lib', 'conf', 'preinitializer.rb')
49
+ puts "cp #{gem_preinitializer} #{preinitializer}"
50
+ cp(gem_preinitializer, preinitializer)
51
+ end
52
+
47
53
  main_env_file = File.join(config_base, "environment.rb")
48
54
  env_contents = File.open(main_env_file).read
49
55
  if !env_contents.include?("require File.join(File.dirname(__FILE__), 'postboot')")
data/lib/conf/postboot.rb CHANGED
@@ -6,20 +6,9 @@ env_dir = File.join(RAILS_ROOT, 'config', rails_env)
6
6
  db_file = File.join(env_dir, 'database.yml')
7
7
  env_file = File.join(env_dir, 'environment.rb')
8
8
 
9
- unless File.exists?(env_dir)
10
- puts "#{env_dir} environment directory cannot be found."
11
- exit(1)
12
- end
13
-
14
- unless File.exists?(db_file)
15
- puts "#{db_file} is missing. You cannot continue without this."
16
- exit(1) # exit with an error code
17
- end
18
-
19
- unless File.exists?(env_file)
20
- puts "#{env_file} environment file is missing."
21
- exit(1)
22
- end
9
+ raise "#{env_dir} environment directory cannot be found." unless File.exists?(env_dir)
10
+ raise "#{db_file} is missing. You cannot continue without this." unless File.exists?(db_file)
11
+ raise "#{env_file} environment file is missing." unless File.exists?(env_file)
23
12
 
24
13
  # Now, let's open up Rails and tell it to find our environment files elsewhere.
25
14
  module Rails
@@ -0,0 +1,20 @@
1
+ # Ensure that proper versions of gems in config/geminstaller.yml are activated.
2
+ require 'rubygems'
3
+ gem 'rails', '= 2.3.0'
4
+ gem 'geminstaller', '= 0.5.2'
5
+ require 'geminstaller'
6
+
7
+ rails_env = ENV['RAILS_ENV'] || 'development'
8
+
9
+ perform_install = %w(development test).include?(rails_env)
10
+
11
+ # Activate gems
12
+ common_gemfile = File.join(RAILS_ROOT, 'config', 'geminstaller.yml')
13
+ env_gemfile = File.join(RAILS_ROOT, "config", rails_env, "geminstaller.yml")
14
+
15
+ [common_gemfile, env_gemfile].each do |file|
16
+ if File.exists?(file)
17
+ GemInstaller.install("--exceptions --config=#{common_gemfile}") if perform_install
18
+ GemInstaller.autogem("--exceptions --config=#{common_gemfile}")
19
+ end
20
+ end
@@ -0,0 +1,256 @@
1
+ == Welcome to Rails
2
+
3
+ Rails is a web-application framework that includes everything needed to create
4
+ database-backed web applications according to the Model-View-Control pattern.
5
+
6
+ This pattern splits the view (also called the presentation) into "dumb" templates
7
+ that are primarily responsible for inserting pre-built data in between HTML tags.
8
+ The model contains the "smart" domain objects (such as Account, Product, Person,
9
+ Post) that holds all the business logic and knows how to persist themselves to
10
+ a database. The controller handles the incoming requests (such as Save New Account,
11
+ Update Product, Show Post) by manipulating the model and directing data to the view.
12
+
13
+ In Rails, the model is handled by what's called an object-relational mapping
14
+ layer entitled Active Record. This layer allows you to present the data from
15
+ database rows as objects and embellish these data objects with business logic
16
+ methods. You can read more about Active Record in
17
+ link:files/vendor/rails/activerecord/README.html.
18
+
19
+ The controller and view are handled by the Action Pack, which handles both
20
+ layers by its two parts: Action View and Action Controller. These two layers
21
+ are bundled in a single package due to their heavy interdependence. This is
22
+ unlike the relationship between the Active Record and Action Pack that is much
23
+ more separate. Each of these packages can be used independently outside of
24
+ Rails. You can read more about Action Pack in
25
+ link:files/vendor/rails/actionpack/README.html.
26
+
27
+
28
+ == Getting Started
29
+
30
+ 1. At the command prompt, start a new Rails application using the <tt>rails</tt> command
31
+ and your application name. Ex: rails myapp
32
+ 2. Change directory into myapp and start the web server: <tt>script/server</tt> (run with --help for options)
33
+ 3. Go to http://localhost:3000/ and get "Welcome aboard: You're riding the Rails!"
34
+ 4. Follow the guidelines to start developing your application
35
+
36
+
37
+ == Web Servers
38
+
39
+ By default, Rails will try to use Mongrel and lighttpd if they are installed, otherwise
40
+ Rails will use WEBrick, the webserver that ships with Ruby. When you run script/server,
41
+ Rails will check if Mongrel exists, then lighttpd and finally fall back to WEBrick. This ensures
42
+ that you can always get up and running quickly.
43
+
44
+ Mongrel is a Ruby-based webserver with a C component (which requires compilation) that is
45
+ suitable for development and deployment of Rails applications. If you have Ruby Gems installed,
46
+ getting up and running with mongrel is as easy as: <tt>gem install mongrel</tt>.
47
+ More info at: http://mongrel.rubyforge.org
48
+
49
+ If Mongrel is not installed, Rails will look for lighttpd. It's considerably faster than
50
+ Mongrel and WEBrick and also suited for production use, but requires additional
51
+ installation and currently only works well on OS X/Unix (Windows users are encouraged
52
+ to start with Mongrel). We recommend version 1.4.11 and higher. You can download it from
53
+ http://www.lighttpd.net.
54
+
55
+ And finally, if neither Mongrel or lighttpd are installed, Rails will use the built-in Ruby
56
+ web server, WEBrick. WEBrick is a small Ruby web server suitable for development, but not
57
+ for production.
58
+
59
+ But of course its also possible to run Rails on any platform that supports FCGI.
60
+ Apache, LiteSpeed, IIS are just a few. For more information on FCGI,
61
+ please visit: http://wiki.rubyonrails.com/rails/pages/FastCGI
62
+
63
+
64
+ == Apache .htaccess example
65
+
66
+ # General Apache options
67
+ AddHandler fastcgi-script .fcgi
68
+ AddHandler cgi-script .cgi
69
+ Options +FollowSymLinks +ExecCGI
70
+
71
+ # If you don't want Rails to look in certain directories,
72
+ # use the following rewrite rules so that Apache won't rewrite certain requests
73
+ #
74
+ # Example:
75
+ # RewriteCond %{REQUEST_URI} ^/notrails.*
76
+ # RewriteRule .* - [L]
77
+
78
+ # Redirect all requests not available on the filesystem to Rails
79
+ # By default the cgi dispatcher is used which is very slow
80
+ #
81
+ # For better performance replace the dispatcher with the fastcgi one
82
+ #
83
+ # Example:
84
+ # RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
85
+ RewriteEngine On
86
+
87
+ # If your Rails application is accessed via an Alias directive,
88
+ # then you MUST also set the RewriteBase in this htaccess file.
89
+ #
90
+ # Example:
91
+ # Alias /myrailsapp /path/to/myrailsapp/public
92
+ # RewriteBase /myrailsapp
93
+
94
+ RewriteRule ^$ index.html [QSA]
95
+ RewriteRule ^([^.]+)$ $1.html [QSA]
96
+ RewriteCond %{REQUEST_FILENAME} !-f
97
+ RewriteRule ^(.*)$ dispatch.cgi [QSA,L]
98
+
99
+ # In case Rails experiences terminal errors
100
+ # Instead of displaying this message you can supply a file here which will be rendered instead
101
+ #
102
+ # Example:
103
+ # ErrorDocument 500 /500.html
104
+
105
+ ErrorDocument 500 "<h2>Application error</h2>Rails application failed to start properly"
106
+
107
+
108
+ == Debugging Rails
109
+
110
+ Sometimes your application goes wrong. Fortunately there are a lot of tools that
111
+ will help you debug it and get it back on the rails.
112
+
113
+ First area to check is the application log files. Have "tail -f" commands running
114
+ on the server.log and development.log. Rails will automatically display debugging
115
+ and runtime information to these files. Debugging info will also be shown in the
116
+ browser on requests from 127.0.0.1.
117
+
118
+ You can also log your own messages directly into the log file from your code using
119
+ the Ruby logger class from inside your controllers. Example:
120
+
121
+ class WeblogController < ActionController::Base
122
+ def destroy
123
+ @weblog = Weblog.find(params[:id])
124
+ @weblog.destroy
125
+ logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
126
+ end
127
+ end
128
+
129
+ The result will be a message in your log file along the lines of:
130
+
131
+ Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1
132
+
133
+ More information on how to use the logger is at http://www.ruby-doc.org/core/
134
+
135
+ Also, Ruby documentation can be found at http://www.ruby-lang.org/ including:
136
+
137
+ * The Learning Ruby (Pickaxe) Book: http://www.ruby-doc.org/docs/ProgrammingRuby/
138
+ * Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
139
+
140
+ These two online (and free) books will bring you up to speed on the Ruby language
141
+ and also on programming in general.
142
+
143
+
144
+ == Debugger
145
+
146
+ Debugger support is available through the debugger command when you start your Mongrel or
147
+ Webrick server with --debugger. This means that you can break out of execution at any point
148
+ in the code, investigate and change the model, AND then resume execution!
149
+ You need to install ruby-debug to run the server in debugging mode. With gems, use 'gem install ruby-debug'
150
+ Example:
151
+
152
+ class WeblogController < ActionController::Base
153
+ def index
154
+ @posts = Post.find(:all)
155
+ debugger
156
+ end
157
+ end
158
+
159
+ So the controller will accept the action, run the first line, then present you
160
+ with a IRB prompt in the server window. Here you can do things like:
161
+
162
+ >> @posts.inspect
163
+ => "[#<Post:0x14a6be8 @attributes={\"title\"=>nil, \"body\"=>nil, \"id\"=>\"1\"}>,
164
+ #<Post:0x14a6620 @attributes={\"title\"=>\"Rails you know!\", \"body\"=>\"Only ten..\", \"id\"=>\"2\"}>]"
165
+ >> @posts.first.title = "hello from a debugger"
166
+ => "hello from a debugger"
167
+
168
+ ...and even better is that you can examine how your runtime objects actually work:
169
+
170
+ >> f = @posts.first
171
+ => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
172
+ >> f.
173
+ Display all 152 possibilities? (y or n)
174
+
175
+ Finally, when you're ready to resume execution, you enter "cont"
176
+
177
+
178
+ == Console
179
+
180
+ You can interact with the domain model by starting the console through <tt>script/console</tt>.
181
+ Here you'll have all parts of the application configured, just like it is when the
182
+ application is running. You can inspect domain models, change values, and save to the
183
+ database. Starting the script without arguments will launch it in the development environment.
184
+ Passing an argument will specify a different environment, like <tt>script/console production</tt>.
185
+
186
+ To reload your controllers and models after launching the console run <tt>reload!</tt>
187
+
188
+ == dbconsole
189
+
190
+ You can go to the command line of your database directly through <tt>script/dbconsole</tt>.
191
+ You would be connected to the database with the credentials defined in database.yml.
192
+ Starting the script without arguments will connect you to the development database. Passing an
193
+ argument will connect you to a different database, like <tt>script/dbconsole production</tt>.
194
+ Currently works for mysql, postgresql and sqlite.
195
+
196
+ == Description of Contents
197
+
198
+ app
199
+ Holds all the code that's specific to this particular application.
200
+
201
+ app/controllers
202
+ Holds controllers that should be named like weblogs_controller.rb for
203
+ automated URL mapping. All controllers should descend from ApplicationController
204
+ which itself descends from ActionController::Base.
205
+
206
+ app/models
207
+ Holds models that should be named like post.rb.
208
+ Most models will descend from ActiveRecord::Base.
209
+
210
+ app/views
211
+ Holds the template files for the view that should be named like
212
+ weblogs/index.html.erb for the WeblogsController#index action. All views use eRuby
213
+ syntax.
214
+
215
+ app/views/layouts
216
+ Holds the template files for layouts to be used with views. This models the common
217
+ header/footer method of wrapping views. In your views, define a layout using the
218
+ <tt>layout :default</tt> and create a file named default.html.erb. Inside default.html.erb,
219
+ call <% yield %> to render the view using this layout.
220
+
221
+ app/helpers
222
+ Holds view helpers that should be named like weblogs_helper.rb. These are generated
223
+ for you automatically when using script/generate for controllers. Helpers can be used to
224
+ wrap functionality for your views into methods.
225
+
226
+ config
227
+ Configuration files for the Rails environment, the routing map, the database, and other dependencies.
228
+
229
+ db
230
+ Contains the database schema in schema.rb. db/migrate contains all
231
+ the sequence of Migrations for your schema.
232
+
233
+ doc
234
+ This directory is where your application documentation will be stored when generated
235
+ using <tt>rake doc:app</tt>
236
+
237
+ lib
238
+ Application specific libraries. Basically, any kind of custom code that doesn't
239
+ belong under controllers, models, or helpers. This directory is in the load path.
240
+
241
+ public
242
+ The directory available for the web server. Contains subdirectories for images, stylesheets,
243
+ and javascripts. Also contains the dispatchers and the default HTML files. This should be
244
+ set as the DOCUMENT_ROOT of your web server.
245
+
246
+ script
247
+ Helper scripts for automation and generation.
248
+
249
+ test
250
+ Unit and functional tests along with fixtures. When using the script/generate scripts, template
251
+ test files will be generated for you and placed in this directory.
252
+
253
+ vendor
254
+ External libraries that the application depends on. Also includes the plugins subdirectory.
255
+ If the app has frozen rails, those gems also go here, under vendor/rails/.
256
+ This directory is in the load path.