1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Ruby on Rails
Find a file
Matthew Draper a6d4e5e532 Internal test migrations use the private 'Current' version
Apart from specific versioning support, our tests should focus on the
behaviour of whatever version they're accompanying, regardless of when
they were written.

Application code should *not* do this.
2015-12-15 17:18:09 +10:30
actionmailer [ci skip] Add a dollar sign to each command in the READMEs 2015-12-06 19:18:52 +01:00
actionpack Merge pull request #22564 from maximeg/legit_name_errors 2015-12-14 10:17:42 -07:00
actionview [ci skip] Add a dollar sign to each command in the READMEs 2015-12-06 19:18:52 +01:00
activejob [ci skip] Add a dollar sign to each command in the READMEs 2015-12-06 19:18:52 +01:00
activemodel ActiveRecord::Base#becomes should copy the errors 2015-12-14 19:02:20 +03:00
activerecord Internal test migrations use the private 'Current' version 2015-12-15 17:18:09 +10:30
activesupport lazy load listen in core 2015-12-13 18:59:34 +01:00
ci Partially revert 14b20ce 2015-11-27 01:32:38 -08:00
guides Use a deliberately-invalid migration version in all doc examples 2015-12-15 17:18:09 +10:30
railties Internal test migrations use the private 'Current' version 2015-12-15 17:18:09 +10:30
tasks Ignore Gemfile.lock in the release task 2015-11-12 15:12:34 -02:00
tools make it possible to customize the executable inside rereun snippets. 2015-06-13 11:58:43 +02:00
.gitignore .gitignore: Ignore .ruby-version in any subdir 2015-09-07 16:37:14 -07:00
.travis.yml Fix travis matrix 2015-12-14 23:45:25 -02:00
.yardopts
CODE_OF_CONDUCT.md Move the CoC text to the Rails website 2015-08-21 12:32:59 -07:00
CONTRIBUTING.md Add specific bug reporting guidelines to contributing.md. [ci skip] 2015-12-11 21:34:42 -05:00
Gemfile lazy load listen in core 2015-12-13 18:59:34 +01:00
Gemfile.lock Update nokogiri to 1.6.7 2015-12-10 13:46:08 -05:00
load_paths.rb require "rubygems" is obsolete in Ruby 1.9.3 2012-05-13 14:47:25 +02:00
rails.gemspec Require sprockets-rails >= 2 2015-09-01 09:30:38 -07:00
RAILS_VERSION Start Rails 5 development 🎉 2014-11-28 15:00:06 -02:00
Rakefile Remove required sdoc from Rakefile 2015-10-26 11:51:05 +01:00
README.md Added dollarsign to the README.md for consistancy 2015-11-28 16:38:51 -08:00
RELEASING_RAILS.md Convert Releasing Rails guide to Markdown 2015-08-15 09:21:46 -04:00
version.rb Start Rails 5 development 🎉 2014-11-28 15:00:06 -02:00

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 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 README.

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 them, 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; 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.

Getting Started

  1. Install Rails at the command prompt if you haven't yet:

     $ gem install rails
    
  2. At the command prompt, create a new Rails application:

     $ rails new myapp
    

    where "myapp" is the application name.

  3. Change directory to myapp and start the web server:

     $ cd myapp
     $ rails server
    

    Run with --help or -h for options.

  4. Using a browser, go to http://localhost:3000 and you'll see: "Welcome aboard: You're riding Ruby on Rails!"

  5. 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!

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.

Code Status

Build Status

License

Ruby on Rails is released under the MIT License.