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
eileencodes 3979403781 Change the protect_from_forgery prepend default to false
Per this comment
https://github.com/rails/rails/pull/18334#issuecomment-69234050 we want
`protect_from_forgery` to default to `prepend: false`.

`protect_from_forgery` will now be insterted into the callback chain at the
point it is called in your application. This is useful for cases where you
want to `protect_from_forgery` after you perform required authentication
callbacks or other callbacks that are required to run after forgery protection.

If you want `protect_from_forgery` callbacks to always run first, regardless of
position they are called in your application, then you can add `prepend: true`
to your `protect_from_forgery` call.

Example:

```ruby
protect_from_forgery prepend: true
```
2015-12-07 10:38:26 -05:00
actionmailer [ci skip] Add a dollar sign to each command in the READMEs 2015-12-06 19:18:52 +01:00
actionpack Change the protect_from_forgery prepend default to false 2015-12-07 10:38:26 -05: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 Merge pull request #22517 from Elektron1c97/master 2015-12-07 01:07:09 -02:00
activerecord Merge pull request #22523 from Elektron1c97/master 2015-12-07 11:15:26 -02:00
activesupport Merge pull request #22517 from Elektron1c97/master 2015-12-07 01:07:09 -02:00
ci Partially revert 14b20ce 2015-11-27 01:32:38 -08:00
guides Introduce after_{create,update,delete}_commit callbacks 2015-12-06 20:33:36 +02:00
railties Merge pull request #22508 from y-yagi/remove_request_forgery_protection_from_rails_api 2015-12-07 12:32:16 -03:00
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 Remove JRUBY_OPTS from .travis.yml file 2015-10-23 10:46:51 +02:00
.yardopts Let YARD document the railties gem 2010-09-09 18:24:34 -07:00
CODE_OF_CONDUCT.md Move the CoC text to the Rails website 2015-08-21 12:32:59 -07: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 Revert "Add prepared statements support for Mysql2Adapter" 2015-11-26 11:53:10 -07:00
Gemfile.lock Revert "Add prepared statements support for Mysql2Adapter" 2015-11-26 11:53:10 -07: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.