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
2016-07-02 18:16:04 +09:00
.github fix typo in pull_request_template [ci skip] 2016-02-26 16:40:42 +09:00
actioncable close hijacked i/o socket after use (fixes #25613) 2016-07-01 23:03:30 +02:00
actionmailer Do not suggest nonsensical OpenSSL verify modes [ci skip] 2016-06-07 15:50:46 +02:00
actionpack Merge pull request #24177 from vipulnsward/rename-test 2016-07-01 23:53:34 -03:00
actionview Merge pull request #25553 from vipulnsward/25543-docs-follow-up 2016-06-30 18:55:13 -07:00
activejob Fix jobs overriding AJ::Base#logger 2016-06-17 13:04:17 -04:00
activemodel Merge pull request #25364 from kamipo/fix_serialize_for_date_type 2016-06-28 23:33:31 -03:00
activerecord Merge pull request #25507 from bquorning/optimize-for-first-result-and-remove-mysql-select_one 2016-07-02 00:06:04 -03:00
activesupport Merge pull request #25625 from voxik/fix-rails-test-git-layout 2016-07-01 21:18:12 -03:00
ci CI: run Action Cable browser tests in Sauce Labs 2016-05-25 09:21:28 -07:00
guides Deprecation passing of start value was removed [ci skip] 2016-07-01 14:18:24 +09:00
railties refer to rails command instead of rake in doc of SourceAnnotationExtractor [ci skip] 2016-07-02 18:16:04 +09:00
tasks Fix release task now that NPM is part of the build 2016-07-01 10:58:06 -04:00
tools Remove requiring load_paths from tools/test.rb 2016-03-02 10:28:34 +05:30
.codeclimate.yml Move code style configuration files to root directory 2016-06-16 22:17:46 -04:00
.gitattributes adds .gitattributes to enable Ruby-awareness 2016-03-16 11:15:22 +01:00
.gitignore .gitignore: Ignore .ruby-version in any subdir 2015-09-07 16:37:14 -07:00
.rubocop.yml Move code style configuration files to root directory 2016-06-16 22:17:46 -04:00
.travis.yml Revert "Merge pull request #25131 from javierhonduco/javierhonduco/clone_depth_to_1" 2016-06-29 01:46:22 +09:30
.yardopts
CODE_OF_CONDUCT.md Move the CoC text to the Rails website 2015-08-21 12:32:59 -07:00
CONTRIBUTING.md Add notes on cosmetic patches 2016-05-13 15:03:50 -04:00
Gemfile Use sass-rails in our test suite 2016-06-30 19:39:37 -03:00
Gemfile.lock Use sass-rails in our test suite 2016-06-30 19:39:37 -03:00
rails.gemspec revises the homepage URL in the gemspecs [ci skip] 2016-03-10 07:55:27 +01:00
RAILS_VERSION Start Rails 5.1 development 🎉 2016-05-10 03:46:56 -03:00
Rakefile Cable: add isolated tests and FAYE=1 test runs 2016-03-20 17:00:46 -07:00
README.md Fix title of README according to Markdown conventions 2016-02-25 03:39:02 +01:00
RELEASING_RAILS.md fix grammar 2016-05-31 13:31:18 +05:30
version.rb Start Rails 5.1 development 🎉 2016-05-10 03:46:56 -03: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.