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
Aaron Patterson 867810cdfa set route precedence at allocation time
This way we can make the Route object a read-only data structure.
2015-08-20 15:34:18 -07:00
actionmailer Removed mocha from ActionMailer 2015-08-20 11:27:49 +05:30
actionpack set route precedence at allocation time 2015-08-20 15:34:18 -07:00
actionview fix Docs [ci skip] 2015-08-18 00:41:17 +05:30
activejob Fix typo on method name 2015-08-16 19:28:32 -03:00
activemodel Rename match_attribute_method? to matched_attribute_method 2015-08-12 00:23:12 +02:00
activerecord uniqueness validation raises error for persisted record without pk. 2015-08-20 12:07:02 +02:00
activesupport Merge pull request #16245 from byroot/more-atomic-write 2015-08-21 01:32:43 +09:30
ci Add the bug report templates to the Travis CI build 2015-06-05 15:29:48 -05:00
guides argh!!! 2015-08-20 13:55:48 -07:00
railties smooth move aaron.... 💣 2015-08-20 13:49:05 -07:00
tasks
tools make it possible to customize the executable inside rereun snippets. 2015-06-13 11:58:43 +02:00
.gitignore Track Gemfile.lock at the repository 2015-02-18 15:14:46 -02:00
.travis.yml Remove JRuby and Rubinius from the travis matrix 2015-07-13 16:59:39 -03:00
.yardopts
CODE_OF_CONDUCT.md Adds a code of conduct 2015-08-18 11:39:17 -05:00
CONTRIBUTING.md Changed 'ask the rubyonrails-talk mailing list.' to 'ask it on the rubyonrails-talk mailing list.' 2015-05-03 16:16:03 +05:30
Gemfile point at rack master 2015-08-20 13:45:11 -07:00
Gemfile.lock point at rack master 2015-08-20 13:45:11 -07:00
load_paths.rb
rails.gemspec Upgrade to Ruby 2.2.2 2015-04-14 08:41:56 +05:30
RAILS_VERSION
Rakefile
README.md Add code of conduct to README.md and to contributing guide [ci skip] 2015-08-18 19:53:31 -04:00
RELEASING_RAILS.md Convert Releasing Rails guide to Markdown 2015-08-15 09:21:46 -04:00
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 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, 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.