Go to file
Sean Griffin 12e5cb5db3 Replace the giant comment in routes.rb with a link to the guides
This comment not only serves no purpose, but in my experience is
actively detrimental to new developers getting started with Rails.
Expereinced developers just end up deleting this comment, and are
annoyed that they had to take this step. I also spend a lot of time
mentoring brand new developers, and a consistent theme I've seen is that
this comment just ends up intimidating them, and making them think it's
dangerous to edit this file.

One of my students just said this (due to the number of comments which
even new developers don't actually read, they just see it as a sign that
this thing is "dangerous").

> I don't edit any file that Rails generates for me, until my instructor
> says that it's OK to do so.

Realistically, this comment adds 0 value. We have very good
documentation, which we can just link to instead. If someone is truly
new enough to benefit from this info, they presumably just ran `gem
install rails`, and have an internet connection that they can use to
read the routing guide.

The choice of language here was very specific. I chose "the DSL
available" over "what is possible", because a consistent theme I've
noticed among my students is that they aren't aware that this is
actually a Ruby file, and can write any Ruby code here that they want.

This file is not the only offender, but is by far the biggest point of
pain that I've seen, and felt it was a good spot to open this
discussion.
2015-07-24 17:22:22 -06:00
actionmailer Revert "Merge pull request #20758 from xijo/action_mailer_message_delivery_respects_i18n_locale" 2015-07-07 22:11:20 +02:00
actionpack rm deep_munge. You will live on in our hearts (and git history) 2015-07-21 18:14:18 -07:00
actionview Merge pull request #20895 from brian-davis/brian-davis 2015-07-20 08:36:49 -06:00
activejob Improve error message when serializing unsaved records for jobs 2015-06-28 14:58:01 -04:00
activemodel Freeze string literals when not mutated. 2015-07-19 17:45:10 -05:00
activerecord destroy shouldn't raise when child associations fail to save 2015-07-24 09:13:20 -06:00
activesupport Merge pull request #20928 from matthewd/unload-interlock 2015-07-24 09:56:20 +09:30
ci Add the bug report templates to the Travis CI build 2015-06-05 15:29:48 -05:00
guides Fix minor typo in testing guide 2015-07-20 13:08:08 -04:00
railties Replace the giant comment in routes.rb with a link to the guides 2015-07-24 17:22:22 -06:00
tasks activejob needs to be built before actionmailer 2014-12-19 16:12:32 -08:00
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 Let YARD document the railties gem 2010-09-09 18:24:34 -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 Add gemfile entry for GlobalID until a new release is cut. 2015-07-05 14:50:33 +02:00
Gemfile.lock Fix Gemfile.lock 2015-07-14 15:20:15 -03:00
install.rb Use --no-document option instead of --no-rdoc and --no-ri option 2015-06-01 22:26:22 +09:00
load_paths.rb require "rubygems" is obsolete in Ruby 1.9.3 2012-05-13 14:47:25 +02:00
RAILS_VERSION Start Rails 5 development 🎉 2014-11-28 15:00:06 -02:00
rails.gemspec Upgrade to Ruby 2.2.2 2015-04-14 08:41:56 +05:30
Rakefile Remove activejob integration tests 2014-08-12 10:07:21 +00:00
README.md Remove bullet 2014-12-21 16:28:25 -04:00
RELEASING_RAILS.rdoc Rails documentation standard is american english. [ci skip] 2015-05-14 01:33:43 +05:30
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, 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.