Ruby on Rails
Go to file
Genadi Samokovarov f46b198142 Web Console documentation for the upcoming 2.1 release [ci skip]
With the upcoming 2.1 [web-console release], I have tweaked the existing
documentation a bit. I tried to focus on the spawning console use case,
because I think a lot of people overlook that.

Tried to explain it as best as I can, however, my English and prose
aren't my best skills :) If you guys can chime in and help me improve
the wording, I would be extremely grateful.

There has been some configuration default changes. For example, the
whitelisted IPs always include IPv4 and IPv6 localhosts now and this
wasn't the case in 2.0. I think a lot of people got bitten by it, that's
why I changed it. I'm a bit confused on how to document this. Should I
just document the latest version, I don't think I can expect all the
people reading the guide to be on it.

[web-console release]: https://github.com/rails/web-console/pull/110
2015-03-02 13:53:51 +02:00
actionmailer Merge pull request #18393 from y-yagi/fix_mailer 2015-02-18 19:05:07 -02:00
actionpack Add a failing test demonstrating regression with HEAD requests to Rack apps, re #18764 2015-02-24 15:59:21 -07:00
actionview Error message testing fix 2015-02-20 21:23:36 -02:00
activejob Avoid creating an extra hash on the job test adapter 2015-02-24 07:23:05 -03:00
activemodel activemodel: make .model_name json encodable 2015-02-24 11:00:32 -07:00
activerecord cache quoted column names in SQLite3 2015-02-24 18:28:00 -08:00
activesupport some indenting and punctuation fixes. [ci skip] 2015-02-23 16:54:40 +01:00
ci Pass symbol as an argument instead of a block 2014-11-29 11:53:24 +01:00
guides Web Console documentation for the upcoming 2.1 release [ci skip] 2015-03-02 13:53:51 +02:00
railties fix typo [ci-skip] 2015-02-25 00:25:58 -06:00
tasks activejob needs to be built before actionmailer 2014-12-19 16:12:32 -08:00
tools minor docs change [ci skip] 2014-11-03 12:37:39 +05:30
.gitignore Track Gemfile.lock at the repository 2015-02-18 15:14:46 -02:00
.travis.yml Track Gemfile.lock at the repository 2015-02-18 15:14:46 -02:00
.yardopts Let YARD document the railties gem 2010-09-09 18:24:34 -07:00
CONTRIBUTING.md Changed "in GitHub" to "on GitHub" [ci skip] 2015-01-14 16:37:36 +05:30
Gemfile Format the time string according to the precision of the time column 2015-02-20 10:25:31 +09:00
Gemfile.lock Format the time string according to the precision of the time column 2015-02-20 10:25:31 +09:00
RAILS_VERSION Start Rails 5 development 🎉 2014-11-28 15:00:06 -02:00
README.md Remove bullet 2014-12-21 16:28:25 -04:00
RELEASING_RAILS.rdoc Remove note about supported plugins from the releasing docs 2015-01-09 22:42:29 -02:00
Rakefile Remove activejob integration tests 2014-08-12 10:07:21 +00:00
install.rb Added activejob to install.rb 2014-08-12 15:37:18 +03:00
load_paths.rb require "rubygems" is obsolete in Ruby 1.9.3 2012-05-13 14:47:25 +02:00
rails.gemspec Remove documentation tasks 2015-02-06 21:04:54 +01:00
version.rb Start Rails 5 development 🎉 2014-11-28 15:00:06 -02:00

README.md

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!

Code Status

Build Status

License

Ruby on Rails is released under the MIT License.