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
Sam Phippen a887c9cbb0 Allow the integration_sesion to be set early on ActionDispatch::Integration::Runner.
In commit fa63448420, @tenderlove changed
the behaviour of the way `integration_session` is set up in this object.
It used to be the case that the first time it was accessed, it was
memoized with nil, however, this means that if it had already been set
it was not replaced. After that commit, it is now always set to `nil` in
the execution of `before_setup`.

In RSpec, users are able to invoke `host!` in `before(:all)` blocks,
which execute well before `before_setup` is ever invoked (which happens
in what is equivalent to a `before(:each)` block, for each test. `host!`
causes the integration session to be set up to correctly change the
host, but after fa63448420 the
`integration_session` gets overwritten, meaning that users lose their
`host!` configuration (see https://github.com/rspec/rspec-rails/issues/1662).

This commit changes the behaviour back to memoizing with `nil`, as
opposed to directly overwriting with `nil`. This causes the correct
behaviour to occur in RSpec, and unless I'm mistaken will also ensure
that users who want to modify their integration sessions early in rails
will also be able to do so.
2016-08-20 14:41:37 +01:00
.github Add a note about adding CHANGELOG entries at the top of the file [ci skip] 2016-07-02 22:31:09 +05:30
actioncable Add three new rubocop rules 2016-08-16 04:30:11 -03:00
actionmailer Add three new rubocop rules 2016-08-16 04:30:11 -03:00
actionpack Allow the integration_sesion to be set early on ActionDispatch::Integration::Runner. 2016-08-20 14:41:37 +01:00
actionview Add three new rubocop rules 2016-08-16 04:30:11 -03:00
activejob correct exception class in retry_on example [ci skip] 2016-08-20 17:21:14 +09:00
activemodel Add three new rubocop rules 2016-08-16 04:30:11 -03:00
activerecord Fix OID::Bit#cast_value 2016-08-20 08:56:54 +09:00
activesupport Merge pull request #25628 from ysksn/options 2016-08-17 02:55:58 -03:00
ci normalizes indentation and whitespace across the project 2016-08-06 20:16:27 +02:00
guides Merge pull request #26224 from jonatack/consistent-asset-precompile-examples 2016-08-19 16:52:16 -04:00
railties Merge pull request #26224 from jonatack/consistent-asset-precompile-examples 2016-08-19 16:52:16 -04:00
tasks modernizes hash syntax in the rest of the project 2016-08-06 19:40:54 +02:00
tools Add three new rubocop rules 2016-08-16 04:30:11 -03:00
.codeclimate.yml Generators and tests are under the same style rules 2016-07-27 20:26:39 -03:00
.gitattributes
.gitignore
.rubocop.yml Add three new rubocop rules 2016-08-16 04:30:11 -03:00
.travis.yml Try the newest bundler 2016-07-02 00:58:54 -03:00
.yardopts
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Gemfile applies new string literal convention in Gemfile 2016-08-06 19:23:19 +02:00
Gemfile.lock Add accidentally removed dependency in Gemfile.lock 2016-08-04 07:55:47 +09:00
rails.gemspec applies new string literal convention in the gemspecs 2016-08-06 19:27:12 +02:00
RAILS_VERSION
Rakefile modernizes hash syntax in the rest of the project 2016-08-06 19:40:54 +02:00
README.md
RELEASING_RAILS.md
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, 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.