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
Sean Griffin 17b09f4fca Merge pull request #27278 from kamipo/should_be_sync_primary_key_definition
Should be sync the `primary_key` definition with actually created
2016-12-08 13:15:13 -05: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 ActionCable::Connection::Base doc code sample syntax error 2016-12-06 10:35:36 -06:00
actionmailer update bin/test scripts to prevent double runs. 2016-11-21 17:25:12 +01:00
actionpack Only move fixture_file_upload to IntegrationTest 2016-12-07 14:03:57 +10:30
actionview Merge pull request #27271 from printercu/permantent_digest_in_tests 2016-12-08 01:29:54 +10:30
activejob Avoid race condition in AJ integration tests 2016-11-30 21:10:52 +10:30
activemodel Merge pull request #27185 from kamipo/fix_apply_seconds_precision 2016-12-08 13:04:39 -05:00
activerecord Merge pull request #27278 from kamipo/should_be_sync_primary_key_definition 2016-12-08 13:15:13 -05:00
activesupport stop using removed render :text 2016-12-03 15:28:59 +09:00
ci Add more rubocop rules about whitespaces 2016-10-29 01:17:49 -02:00
guides stop using removed render :text 2016-12-03 15:28:59 +09:00
railties Update puma.rb 2016-12-05 16:48:25 -08:00
tasks modernizes hash syntax in the rest of the project 2016-08-06 19:40:54 +02:00
tools update bin/test scripts to prevent double runs. 2016-11-21 17:25:12 +01:00
.codeclimate.yml Generators and tests are under the same style rules 2016-07-27 20:26:39 -03:00
.gitattributes adds .gitattributes to enable Ruby-awareness 2016-03-16 11:15:22 +01:00
.gitignore Make pg adapter use bigserial for pk by default 2016-12-05 11:40:32 -08:00
.rubocop.yml Add more rubocop rules about whitespaces 2016-10-29 01:17:49 -02:00
.travis.yml Only start rabbitmq when we need it 2016-11-27 17:50:17 +10:30
.yardopts
CODE_OF_CONDUCT.md
CONTRIBUTING.md Add notes on cosmetic patches 2016-05-13 15:03:50 -04:00
Gemfile rails-ujs is now shipped with Action View 2016-11-29 09:48:19 -05:00
Gemfile.lock rails-ujs is now shipped with Action View 2016-11-29 09:48:19 -05:00
MIT-LICENSE Rename LICENSE to MIT-LICENSE for consistency with sub projects 2016-09-23 12:00:19 -07:00
rails.gemspec applies new string literal convention in the gemspecs 2016-08-06 19:27:12 +02:00
RAILS_VERSION Start Rails 5.1 development 🎉 2016-05-10 03:46:56 -03:00
Rakefile Remove Faye mode 2016-10-01 15:35:59 +09:30
README.md Fix title of README according to Markdown conventions 2016-02-25 03:39:02 +01:00
RELEASING_RAILS.md Update RELEASING_RAILS.md for rails-ujs 2016-11-26 10:51:44 -05:00
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.