50311f1391
Previously when app was mounted as following:
class Foo
def call(env)
[200, {}, [env['PATH_INFO']]]
end
end
RackMountRailsBug::Application.routes.draw do
mount RackTest.new => "/foo"
end
trailing slash was removed from PATH_INFO. For example requesting
GET /foo/bar/
on routes defined above would result in a response containing "/foo/bar"
instead of "/foo/bar/".
This commit fixes the issue.
(closes #3215)
|
||
|---|---|---|
| actionmailer | ||
| actionpack | ||
| actionview | ||
| activemodel | ||
| activerecord | ||
| activesupport | ||
| ci | ||
| guides | ||
| railties | ||
| tasks | ||
| tools | ||
| .gitignore | ||
| .travis.yml | ||
| .yardopts | ||
| CONTRIBUTING.md | ||
| Gemfile | ||
| install.rb | ||
| load_paths.rb | ||
| RAILS_VERSION | ||
| rails.gemspec | ||
| Rakefile | ||
| README.md | ||
| RELEASING_RAILS.rdoc | ||
| version.rb | ||
Welcome to Rails
Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.
Understanding the MVC pattern is key to understanding Rails. MVC divides your application into three layers, each with a specific responsibility.
The View layer is composed of "templates" that are responsible for providing appropriate representations of your application's resources. Templates can come in a variety of formats, but most view templates are HTML with embedded Ruby code (ERB files).
The Model layer represents your domain model (such as Account, Product,
Person, Post, etc.) and encapsulates the business logic that is specific to
your application. In Rails, database-backed model classes are derived from
ActiveRecord::Base. Active Record allows you to present the data from
database rows as objects and embellish these data objects with business logic
methods. Although most Rails models are backed by a database, models can also
be ordinary Ruby classes, or Ruby classes that implement a set of interfaces
as provided by the Active Model module. You can read more about Active Record
in its README.
The Controller layer is responsible for handling incoming HTTP requests and providing a suitable response. Usually this means returning HTML, but Rails controllers can also generate XML, JSON, PDFs, mobile-specific views, and more. Controllers manipulate models and render view templates in order to generate the appropriate HTTP response.
In Rails, the Controller and View layers are handled together by Action Pack. These two layers are bundled in a single package due to their heavy interdependence. This is unlike the relationship between Active Record and Action Pack, which are independent. Each of these packages can be used independently outside of Rails. You can read more about Action Pack in its README.
Getting Started
-
Install Rails at the command prompt if you haven't yet:
gem install rails -
At the command prompt, create a new Rails application:
rails new myappwhere "myapp" is the application name.
-
Change directory to
myappand start the web server:cd myapp rails serverRun with
--helpor-hfor options. -
Go to http://localhost:3000 and you'll see: "Welcome aboard: You're riding Ruby on Rails!"
-
Follow the guidelines to start developing your application. You may find the following resources handy:
Contributing
We encourage you to contribute to Ruby on Rails! Please check out the Contributing to Ruby on Rails guide for guidelines about how to proceed. Join us!
Code Status
License
Ruby on Rails is released under the MIT License.