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
Kasper Timm Hansen 493313228a Rename constrain_to to exclude.
`ActionDispatch::SSL` redirects all HTTP requests to HTTPS, not just some.
The `constrain_to` option inverts this, so it sounds like the middleware
only handles a few requests, rather than the majority with a few routes to
opt out of the redirect.

Renaming to `exclude` matches this intent more closely.
2016-03-03 21:09:58 +01:00
.github fix typo in pull_request_template [ci skip] 2016-02-26 16:40:42 +09:00
actioncable Merge pull request #23992 from matthewd/em-option 2016-03-04 05:31:48 +10:30
actionmailer Change 'a HTML' to 'an HTML' [ci skip] 2016-03-03 19:33:00 +05:30
actionpack Rename constrain_to to exclude. 2016-03-03 21:09:58 +01:00
actionview Fix CHANGELOG spacing [ci skip] 2016-03-02 11:37:19 -07:00
activejob Merge pull request #23932 from arthurnn/arthurnn/remove_load_paths 2016-03-01 16:10:09 -05:00
activemodel Remove load_paths file 2016-02-27 13:03:57 -05:00
activerecord don't treat all associations with extensions as instance dependent. 2016-03-03 16:52:35 +01:00
activesupport Prevent nested ExecutionWrapper calls even when using run! directly 2016-03-04 00:35:43 +10:30
ci Remove commented out code in ci/travis.rb [ci skip] 2016-02-04 09:15:25 +09:00
guides [ci skip] Make collection caching explicit in guides. 2016-03-03 20:53:49 +01:00
railties Fix CHANGELOG spacing [ci skip] 2016-03-02 11:37:19 -07:00
tasks Wrangle the asset build into something that sounds more general 2016-02-01 05:03:03 +10:30
tools Remove requiring load_paths from tools/test.rb 2016-03-02 10:28:34 +05:30
.gitignore .gitignore: Ignore .ruby-version in any subdir 2015-09-07 16:37:14 -07:00
.travis.yml Merge pull request #23992 from matthewd/em-option 2016-03-04 05:31:48 +10:30
.yardopts
CODE_OF_CONDUCT.md Move the CoC text to the Rails website 2015-08-21 12:32:59 -07:00
CONTRIBUTING.md Typo in Contributing.md documentation 2016-01-06 23:34:41 +00:00
Gemfile Update turbolinks-rails for passing railties test 2016-02-05 17:02:22 +05:30
Gemfile.lock Merge pull request #23992 from matthewd/em-option 2016-03-04 05:31:48 +10:30
rails.gemspec Initial stab at adding Action Cable to rails/master 2015-12-14 16:38:37 +01:00
RAILS_VERSION Prep release for Rails 5 beta3 2016-02-24 10:27:02 -05:00
Rakefile Add task to test the release preparation 2015-12-18 14:56:26 -02:00
README.md Fix title of README according to Markdown conventions 2016-02-25 03:39:02 +01:00
RELEASING_RAILS.md Update RELEASING_RAILS.md 2016-02-12 08:38:21 -05:00
version.rb Prep release for Rails 5 beta3 2016-02-24 10:27:02 -05: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 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; 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: "Yay! Youre 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.