From c6f274cd9469e0bb2477255b4abc54e039e60629 Mon Sep 17 00:00:00 2001 From: Matt Di Pasquale Date: Wed, 24 Mar 2010 02:17:09 -0400 Subject: [PATCH 1/5] sync README files & make minor edits --- railties/README | 13 +- .../rails/generators/rails/app/templates/README | 145 +++++++++++++------- 2 files changed, 103 insertions(+), 55 deletions(-) diff --git a/railties/README b/railties/README index e4de4a5..f878139 100644 --- a/railties/README +++ b/railties/README @@ -46,10 +46,10 @@ getting up and running with mongrel is as easy as: gem install mongrel. More info at: http://mongrel.rubyforge.org Other ruby web servers exist which can run your rails application, however rails server does -not search for them or start them. These include {Thin}[http://code.macournoyer.com/thin/], {Ebb}[http://ebb.rubyforge.org/], and Apache with {mod_rails}[http://www.modrails.com/]. +not search for them or start them. These include {Thin}[http://code.macournoyer.com/thin/], {Ebb}[http://ebb.rubyforge.org/], and Apache with {mod_rails}[http://www.modrails.com/]. -For production use, often a web/proxy server such as {Apache}[http://apache.org], {Nginx}[http://nginx.net/], {LiteSpeed}[http://litespeedtech.com/], {Lighttpd}[http://www.lighttpd.net/] or {IIS}[http://www.iis.net/] is -deployed as the front-end server, with the chosen ruby web server running in the back-end +For production use, often a web/proxy server, such as {Apache}[http://apache.org], {Nginx}[http://nginx.net/], {LiteSpeed}[http://litespeedtech.com/], {Lighttpd}[http://www.lighttpd.net/] or {IIS}[http://www.iis.net/], is +deployed as the front-end server with the chosen ruby web server running in the back-end and receiving the proxied requests via one of several protocols (HTTP, CGI, FCGI). @@ -85,12 +85,12 @@ set the RewriteBase in this htaccess file. RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ dispatch.cgi [QSA,L] -Incase Rails experiences terminal errors instead of displaying those messages you -can supply a file here which will be rendered instead. +Incase Rails experiences terminal errors, you may supply a file here to be rendered instead. ErrorDocument 500 /500.html ErrorDocument 500 "

Application error

Rails application failed to start properly" + == Debugging Rails Sometimes your application goes wrong. Fortunately there are a lot of tools that @@ -176,8 +176,11 @@ Options: * Passing an environment name as an argument will load the corresponding environment. Example: rails console production. +To reload your controllers and models after launching the console run reload! + More information about irb can be found at link:http://www.rubycentral.com/pickaxe/irb.html + == dbconsole You can go to the command line of your database directly through rails dbconsole. diff --git a/railties/lib/rails/generators/rails/app/templates/README b/railties/lib/rails/generators/rails/app/templates/README index ded8570..a5e0f44 100644 --- a/railties/lib/rails/generators/rails/app/templates/README +++ b/railties/lib/rails/generators/rails/app/templates/README @@ -1,7 +1,7 @@ == 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. +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. @@ -28,7 +28,7 @@ link:files/vendor/rails/actionpack/README.html. == Getting Started 1. At the command prompt, start a new Rails application using the rails command - and your application name. Ex: rails myapp + and your application name. Ex: rails myapp 2. Change directory into myapp and start the web server: rails server (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 @@ -45,52 +45,50 @@ suitable for development and deployment of Rails applications. If you have Ruby getting up and running with mongrel is as easy as: gem install mongrel. 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. +Other ruby web servers exist which can run your rails application, however rails server does +not search for them or start them. These include {Thin}[http://code.macournoyer.com/thin/], {Ebb}[http://ebb.rubyforge.org/], and Apache with {mod_rails}[http://www.modrails.com/]. + +For production use, often a web/proxy server, such as {Apache}[http://apache.org], {Nginx}[http://nginx.net/], {LiteSpeed}[http://litespeedtech.com/], {Lighttpd}[http://www.lighttpd.net/] or {IIS}[http://www.iis.net/], is +deployed as the front-end server with the chosen ruby web server running in the back-end +and receiving the proxied requests via one of several protocols (HTTP, CGI, FCGI). + == 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 "

Application error

Rails application failed to start properly" +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. + + 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. + + 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. + + 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] + +Incase Rails experiences terminal errors, you may supply a file here to be rendered instead. + + ErrorDocument 500 /500.html + ErrorDocument 500 "

Application error

Rails application failed to start properly" == Debugging Rails @@ -133,7 +131,7 @@ and also on programming in general. 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! +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: @@ -165,14 +163,24 @@ Finally, when you're ready to resume execution, you enter "cont" == Console -You can interact with the domain model by starting the console through rails console. -Here you'll have all parts of the application configured, just like it is when the +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. -Passing an argument will specify a different environment, like rails console production. + +To start the console, just run rails console from the application directory. + +Options: + +* Passing the -s, --sandbox argument will rollback any modifications made to the database. +* Passing an environment name as an argument will load the corresponding environment. + Example: rails console production. To reload your controllers and models after launching the console run reload! +More information about irb can be found at link:http://www.rubycentral.com/pickaxe/irb.html + + == dbconsole You can go to the command line of your database directly through rails dbconsole. @@ -183,6 +191,43 @@ Currently works for mysql, postgresql and sqlite. == Description of Contents +The default directory structure of a generated Ruby on Rails applicartion: + + |-- app + | |-- controllers + | |-- helpers + | |-- models + | `-- views + | `-- layouts + |-- config + | |-- environments + | |-- initializers + | `-- locales + |-- db + |-- doc + |-- lib + | `-- tasks + |-- log + |-- public + | |-- images + | |-- javascripts + | `-- stylesheets + |-- script + | `-- performance + |-- test + | |-- fixtures + | |-- functional + | |-- integration + | |-- performance + | `-- unit + |-- tmp + | |-- cache + | |-- pids + | |-- sessions + | `-- sockets + `-- vendor + `-- plugins + app Holds all the code that's specific to this particular application. -- 1.6.4.4 From c854e325b5086f9a000cdb659a89b14f158b93b2 Mon Sep 17 00:00:00 2001 From: Matt Di Pasquale Date: Wed, 24 Mar 2010 02:21:40 -0400 Subject: [PATCH 2/5] replace README w sym link to original --- railties/README | 290 +------------------------------------------------------ 1 files changed, 1 insertions(+), 289 deletions(-) mode change 100644 => 120000 railties/README diff --git a/railties/README b/railties/README deleted file mode 100644 index f878139..0000000 --- a/railties/README +++ /dev/null @@ -1,289 +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, start a new Rails application using the rails command - and your application name. Ex: rails myapp -2. Change directory into myapp and start the web server: rails server (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 installed when started with rails 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: gem install mongrel. -More info at: http://mongrel.rubyforge.org - -Other ruby web servers exist which can run your rails application, however rails server does -not search for them or start them. These include {Thin}[http://code.macournoyer.com/thin/], {Ebb}[http://ebb.rubyforge.org/], and Apache with {mod_rails}[http://www.modrails.com/]. - -For production use, often a web/proxy server, such as {Apache}[http://apache.org], {Nginx}[http://nginx.net/], {LiteSpeed}[http://litespeedtech.com/], {Lighttpd}[http://www.lighttpd.net/] or {IIS}[http://www.iis.net/], is -deployed as the front-end server with the chosen ruby web server running in the back-end -and receiving the proxied requests via one of several protocols (HTTP, CGI, FCGI). - - -== 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. - - 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. - - 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. - - 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] - -Incase Rails experiences terminal errors, you may supply a file here to be rendered instead. - - ErrorDocument 500 /500.html - ErrorDocument 500 "

Application error

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 - => "[#nil, \"body\"=>nil, \"id\"=>\"1\"}>, - #\"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 - => #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 - -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, just run rails console from the application directory. - -Options: - -* Passing the -s, --sandbox argument will rollback any modifications made to the database. -* Passing an environment name as an argument will load the corresponding environment. - Example: rails console production. - -To reload your controllers and models after launching the console run reload! - -More information about irb can be found at link:http://www.rubycentral.com/pickaxe/irb.html - - -== dbconsole - -You can go to the command line of your database directly through rails dbconsole. -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 rails dbconsole production. -Currently works for mysql, postgresql and sqlite. - -== Description of Contents - -The default directory structure of a generated Ruby on Rails applicartion: - - |-- app - | |-- controllers - | |-- helpers - | |-- models - | `-- views - | `-- layouts - |-- config - | |-- environments - | |-- initializers - | `-- locales - |-- db - |-- doc - |-- lib - | `-- tasks - |-- log - |-- public - | |-- images - | |-- javascripts - | `-- stylesheets - |-- script - | `-- performance - |-- test - | |-- fixtures - | |-- functional - | |-- integration - | |-- performance - | `-- unit - |-- tmp - | |-- cache - | |-- pids - | |-- sessions - | `-- sockets - `-- vendor - `-- plugins - -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 - layout :default 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 rails 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 rake doc:app - -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 rails 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. diff --git a/railties/README b/railties/README new file mode 120000 index 0000000..2b55adb --- /dev/null +++ b/railties/README @@ -0,0 +1 @@ +lib/rails/generators/rails/app/templates/README \ No newline at end of file -- 1.6.4.4 From cad70dd434d09eb30ca623f0fd1840e2ce0b4ef7 Mon Sep 17 00:00:00 2001 From: Matt Di Pasquale Date: Wed, 24 Mar 2010 02:43:23 -0400 Subject: [PATCH 3/5] capitalize ruby & rm double spaces --- .../rails/generators/rails/app/templates/README | 16 ++++++++-------- 1 files changed, 8 insertions(+), 8 deletions(-) diff --git a/railties/lib/rails/generators/rails/app/templates/README b/railties/lib/rails/generators/rails/app/templates/README index a5e0f44..66d8375 100644 --- a/railties/lib/rails/generators/rails/app/templates/README +++ b/railties/lib/rails/generators/rails/app/templates/README @@ -21,7 +21,7 @@ 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 +Rails. You can read more about Action Pack in link:files/vendor/rails/actionpack/README.html. @@ -45,11 +45,11 @@ suitable for development and deployment of Rails applications. If you have Ruby getting up and running with mongrel is as easy as: gem install mongrel. More info at: http://mongrel.rubyforge.org -Other ruby web servers exist which can run your rails application, however rails server does +Other Ruby web servers exist which can run your rails application, however rails server does not search for them or start them. These include {Thin}[http://code.macournoyer.com/thin/], {Ebb}[http://ebb.rubyforge.org/], and Apache with {mod_rails}[http://www.modrails.com/]. For production use, often a web/proxy server, such as {Apache}[http://apache.org], {Nginx}[http://nginx.net/], {LiteSpeed}[http://litespeedtech.com/], {Lighttpd}[http://www.lighttpd.net/] or {IIS}[http://www.iis.net/], is -deployed as the front-end server with the chosen ruby web server running in the back-end +deployed as the front-end server with the chosen Ruby web server running in the back-end and receiving the proxied requests via one of several protocols (HTTP, CGI, FCGI). @@ -93,10 +93,10 @@ Incase Rails experiences terminal errors, you may supply a file here to be rende == Debugging Rails -Sometimes your application goes wrong. Fortunately there are a lot of tools that +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 +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. @@ -121,7 +121,7 @@ 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) +* 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. @@ -163,7 +163,7 @@ Finally, when you're ready to resume execution, you enter "cont" == Console -The console is a ruby shell, which allows you to interact with your application's domain +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. @@ -260,7 +260,7 @@ 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 + Contains the database schema in schema.rb. db/migrate contains all the sequence of Migrations for your schema. doc -- 1.6.4.4 From 6c553f24544ca72990fa8343df50c7bb600fac50 Mon Sep 17 00:00:00 2001 From: Matt Di Pasquale Date: Sat, 27 Mar 2010 10:11:58 -0400 Subject: [PATCH 4/5] replace webserver w/ Web server --- .../rails/generators/rails/app/templates/README | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/railties/lib/rails/generators/rails/app/templates/README b/railties/lib/rails/generators/rails/app/templates/README index 66d8375..193d02f 100644 --- a/railties/lib/rails/generators/rails/app/templates/README +++ b/railties/lib/rails/generators/rails/app/templates/README @@ -37,10 +37,10 @@ link:files/vendor/rails/actionpack/README.html. == Web Servers By default, Rails will try to use Mongrel if it's installed when started with rails server, otherwise -Rails will use WEBrick, the webserver that ships with Ruby. But you can also use Rails +Rails will use WEBrick, the Web server 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 +Mongrel is a Ruby-based Web server 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: gem install mongrel. More info at: http://mongrel.rubyforge.org -- 1.6.4.4 From 4cb1b5ba9a9db289e52387dd235cde126ee53b3b Mon Sep 17 00:00:00 2001 From: Matt Di Pasquale Date: Sat, 27 Mar 2010 10:12:47 -0400 Subject: [PATCH 5/5] rm README symlink --- railties/README | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) delete mode 120000 railties/README diff --git a/railties/README b/railties/README deleted file mode 120000 index 2b55adb..0000000 --- a/railties/README +++ /dev/null @@ -1 +0,0 @@ -lib/rails/generators/rails/app/templates/README \ No newline at end of file -- 1.6.4.4