Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Because Ruby on Rails is slow sometimes
Ruby

This branch is 1267 commits ahead, 24350 commits behind rails:master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
actionmailer
actionpack Merge pull request #8490 from mattv/fix_request_raw_post
activemodel
activerecord
activeresource
activesupport
ci
railties
tasks
tools
.gitignore
.travis.yml
.yardopts
Gemfile
RAILS_VERSION
README.rdoc
RELEASING_RAILS.rdoc
Rakefile
install.rb
load_paths.rb
rails.gemspec
version.rb

README.rdoc

Towards A Better Rails

This is a fork of the Rails 3.2.x stable release in an attempt to simplify and clean up the framework. Initially it will focus on compatible changes but features will likely be removed or tweaked over time. Special attention will be paid to efficiency of the code and how well costs of certain code is management.

This is a long process but we'll start with real needs, optimization of ActiveRecord and the adoption of threading techniques for the newer Ruby VMs. Even though this is based on Rails 3.2, you may consider 1.8 support dropped.

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 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).

The Model layer represents your domain model (such as Account, Product, Person, Post) 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. 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 ActiveModel module. You can read more about Active Record 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 manipulate models and render view templates in order to generate the appropriate HTTP response.

In Rails, the Controller and View layers are handled together by Action Pack. These two layers are bundled in a single package due to their heavy interdependence. This is unlike the relationship between Active Record and Action Pack which are independent. Each of these packages can be used independently outside of Rails. You can read more about Action Pack in its README.

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 for options.

  4. Go to 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:

License

Ruby on Rails is released under the MIT license.

Something went wrong with that request. Please try again.