|Number of watchers on Github||38924|
|Number of open issues||1062|
|Average time to close an issue||about 17 hours|
|Average time to merge a PR||about 18 hours|
|Open pull requests||640+|
|Closed pull requests||344+|
|Last commit||4 months ago|
|Repo Created||over 10 years ago|
|Repo Last Updated||4 months ago|
|Organization / Author||rails|
|Do you use rails? Leave a review!|
|View open issues (1062)|
|View rails activity|
|View TODOs for rails (80)|
|View on github|
|Latest Open Source Launches|
Trendy new open source projects in your inbox! View examples
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 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. You can read more about Active Record in its README.
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 Model 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 load and
manipulate models, and render view templates in order to generate the appropriate HTTP response.
In Rails, incoming requests are routed by Action Dispatch to an appropriate controller, and
controller classes are derived from
ActionController::Base. Action Dispatch and Action Controller
are bundled together in Action Pack. You can read more about Action Pack in its
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). Views are typically rendered to generate a controller response,
or to generate the body of an email. In Rails, View generation is handled by Action View.
You can read more about Action View in its README.
Active Record, Active Model, Action Pack, and Action View can each be used independently outside Rails. In addition to that, Rails also comes with Action Mailer (README), a library to generate and send emails; Active Job (README), a framework for declaring jobs and making them run on a variety of queueing backends; Action Cable (README), a framework to integrate WebSockets with a Rails application; Active Storage (README), a library to attach cloud and local files to Rails applications; and Active Support (README), a collection of utility classes and standard library extensions that are useful for Rails, and may also be used independently outside Rails.
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 myapp
myapp is the application name.
Change directory to
myapp and start the web server:
$ cd myapp $ rails server
-h for options.
Using a browser, go to
http://localhost:3000 and you'll see:
Yay! Youre on Rails!
Follow the guidelines to start developing your application. You may find the following resources handy:
Trying to report a possible security vulnerability in Rails? Please check out our security policy for guidelines about how to proceed.
Everyone interacting in Rails and its sub-projects' codebases, issue trackers, chat rooms, and mailing lists is expected to follow the Rails code of conduct.
Ruby on Rails is released under the MIT License.