GitHub - phry/rails: Ruby on Rails

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

Install Rails at the command prompt if you haven’t yet:
```
geminstallrails
```
At the command prompt, create a new Rails application:
```
railsnewmyapp
```
where “myapp” is the application name.
Change directory to myapp and start the web server:
```
cdmyapp; railsserver
```
Run with --help for options.

Go to localhost:3000 and you’ll see:

"Welcome aboard: You're riding Ruby on Rails!"

Follow the guidelines to start developing your application. You may find the following resources handy:

The README file created within your application.
The Getting Started with Rails.
The Ruby on Rails Tutorial.
The Ruby on Rails Guides.
The API Documentation.

Contributing

We encourage you to contribute to Ruby on Rails! Please check out the Contributing to Rails guide for guidelines about how to proceed. Join us!

Build Status <img src=“https://secure.travis-ci.org/rails/rails.png”/>

Dependency Status <img src=“https://gemnasium.com/rails/rails.png?travis”/>

License

Ruby on Rails is released under the MIT license:

www.opensource.org/licenses/MIT

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

Install Rails at the command prompt if you haven’t yet:
```
geminstallrails
```
At the command prompt, create a new Rails application:
```
railsnewmyapp
```
where “myapp” is the application name.
Change directory to myapp and start the web server:
```
cdmyapp; railsserver
```
Run with --help for options.

Go to localhost:3000 and you’ll see:

"Welcome aboard: You're riding Ruby on Rails!"

Follow the guidelines to start developing your application. You may find the following resources handy:

The README file created within your application.
The Getting Started with Rails.
The Ruby on Rails Tutorial.
The Ruby on Rails Guides.
The API Documentation.

Contributing

We encourage you to contribute to Ruby on Rails! Please check out the Contributing to Rails guide for guidelines about how to proceed. Join us!

Build Status <img src=“https://secure.travis-ci.org/rails/rails.png”/>

Dependency Status <img src=“https://gemnasium.com/rails/rails.png?travis”/>

License

Ruby on Rails is released under the MIT license:

www.opensource.org/licenses/MIT

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

Install Rails at the command prompt if you haven’t yet:
```
geminstallrails
```
At the command prompt, create a new Rails application:
```
railsnewmyapp
```
where “myapp” is the application name.
Change directory to myapp and start the web server:
```
cdmyapp; railsserver
```
Run with --help for options.

Go to localhost:3000 and you’ll see:

"Welcome aboard: You're riding Ruby on Rails!"

Follow the guidelines to start developing your application. You may find the following resources handy:

The README file created within your application.
The Getting Started with Rails.
The Ruby on Rails Tutorial.
The Ruby on Rails Guides.
The API Documentation.

Contributing

We encourage you to contribute to Ruby on Rails! Please check out the Contributing to Rails guide for guidelines about how to proceed. Join us!

Build Status <img src=“https://secure.travis-ci.org/rails/rails.png”/>

Dependency Status <img src=“https://gemnasium.com/rails/rails.png?travis”/>

License

Ruby on Rails is released under the MIT license:

www.opensource.org/licenses/MIT

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

Install Rails at the command prompt if you haven’t yet:
```
geminstallrails
```
At the command prompt, create a new Rails application:
```
railsnewmyapp
```
where “myapp” is the application name.
Change directory to myapp and start the web server:
```
cdmyapp; railsserver
```
Run with --help for options.

Go to localhost:3000 and you’ll see:

"Welcome aboard: You're riding Ruby on Rails!"

Follow the guidelines to start developing your application. You may find the following resources handy:

The README file created within your application.
The Getting Started with Rails.
The Ruby on Rails Tutorial.
The Ruby on Rails Guides.
The API Documentation.

Contributing

We encourage you to contribute to Ruby on Rails! Please check out the Contributing to Rails guide for guidelines about how to proceed. Join us!

Build Status <img src=“https://secure.travis-ci.org/rails/rails.png”/>

Dependency Status <img src=“https://gemnasium.com/rails/rails.png?travis”/>

License

Ruby on Rails is released under the MIT license:

www.opensource.org/licenses/MIT

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

Install Rails at the command prompt if you haven’t yet:
```
geminstallrails
```
At the command prompt, create a new Rails application:
```
railsnewmyapp
```
where “myapp” is the application name.
Change directory to myapp and start the web server:
```
cdmyapp; railsserver
```
Run with --help for options.

Go to localhost:3000 and you’ll see:

"Welcome aboard: You're riding Ruby on Rails!"

Follow the guidelines to start developing your application. You may find the following resources handy:

The README file created within your application.
The Getting Started with Rails.
The Ruby on Rails Tutorial.
The Ruby on Rails Guides.
The API Documentation.

Contributing

We encourage you to contribute to Ruby on Rails! Please check out the Contributing to Rails guide for guidelines about how to proceed. Join us!

Build Status <img src=“https://secure.travis-ci.org/rails/rails.png”/>

Dependency Status <img src=“https://gemnasium.com/rails/rails.png?travis”/>

License

Ruby on Rails is released under the MIT license:

www.opensource.org/licenses/MIT

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

Install Rails at the command prompt if you haven’t yet:
```
geminstallrails
```
At the command prompt, create a new Rails application:
```
railsnewmyapp
```
where “myapp” is the application name.
Change directory to myapp and start the web server:
```
cdmyapp; railsserver
```
Run with --help for options.

Go to localhost:3000 and you’ll see:

"Welcome aboard: You're riding Ruby on Rails!"

Follow the guidelines to start developing your application. You may find the following resources handy:

The README file created within your application.
The Getting Started with Rails.
The Ruby on Rails Tutorial.
The Ruby on Rails Guides.
The API Documentation.

Contributing

We encourage you to contribute to Ruby on Rails! Please check out the Contributing to Rails guide for guidelines about how to proceed. Join us!

Build Status <img src=“https://secure.travis-ci.org/rails/rails.png”/>

Dependency Status <img src=“https://gemnasium.com/rails/rails.png?travis”/>

License

Ruby on Rails is released under the MIT license:

www.opensource.org/licenses/MIT

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

Install Rails at the command prompt if you haven’t yet:
```
geminstallrails
```
At the command prompt, create a new Rails application:
```
railsnewmyapp
```
where “myapp” is the application name.
Change directory to myapp and start the web server:
```
cdmyapp; railsserver
```
Run with --help for options.

Go to localhost:3000 and you’ll see:

"Welcome aboard: You're riding Ruby on Rails!"

Follow the guidelines to start developing your application. You may find the following resources handy:

The README file created within your application.
The Getting Started with Rails.
The Ruby on Rails Tutorial.
The Ruby on Rails Guides.
The API Documentation.

Contributing

We encourage you to contribute to Ruby on Rails! Please check out the Contributing to Rails guide for guidelines about how to proceed. Join us!

Build Status <img src=“https://secure.travis-ci.org/rails/rails.png”/>

Dependency Status <img src=“https://gemnasium.com/rails/rails.png?travis”/>

License

Ruby on Rails is released under the MIT license:

www.opensource.org/licenses/MIT

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

Install Rails at the command prompt if you haven’t yet:
```
geminstallrails
```
At the command prompt, create a new Rails application:
```
railsnewmyapp
```
where “myapp” is the application name.
Change directory to myapp and start the web server:
```
cdmyapp; railsserver
```
Run with --help for options.

Go to localhost:3000 and you’ll see:

"Welcome aboard: You're riding Ruby on Rails!"

Follow the guidelines to start developing your application. You may find the following resources handy:

The README file created within your application.
The Getting Started with Rails.
The Ruby on Rails Tutorial.
The Ruby on Rails Guides.
The API Documentation.

www.opensource.org/licenses/MIT

Name		Name	Last commit message	Last commit date
actionmailer		actionmailer
actionpack		actionpack
activemodel		activemodel
activerecord		activerecord
activesupport		activesupport
ci		ci
railties		railties
tasks		tasks
tools		tools
.gitignore		.gitignore
.travis.yml		.travis.yml
.yardopts		.yardopts
Gemfile		Gemfile
RAILS_VERSION		RAILS_VERSION
README.rdoc		README.rdoc
RELEASING_RAILS.rdoc		RELEASING_RAILS.rdoc
Rakefile		Rakefile
install.rb		install.rb
load_paths.rb		load_paths.rb
rails.gemspec		rails.gemspec
version.rb		version.rb

Name		Name	Last commit message	Last commit date
actionmailer		actionmailer
actionpack		actionpack
activemodel		activemodel
activerecord		activerecord
activesupport		activesupport
ci		ci
railties		railties
tasks		tasks
tools		tools
.gitignore		.gitignore
.travis.yml		.travis.yml
.yardopts		.yardopts
Gemfile		Gemfile
RAILS_VERSION		RAILS_VERSION
README.rdoc		README.rdoc
RELEASING_RAILS.rdoc		RELEASING_RAILS.rdoc
Rakefile		Rakefile
install.rb		install.rb
load_paths.rb		load_paths.rb
rails.gemspec		rails.gemspec
version.rb		version.rb

Name		Name	Last commit message	Last commit date
actionmailer		actionmailer
actionpack		actionpack
activemodel		activemodel
activerecord		activerecord
activesupport		activesupport
ci		ci
railties		railties
tasks		tasks
tools		tools
.gitignore		.gitignore
.travis.yml		.travis.yml
.yardopts		.yardopts
Gemfile		Gemfile
RAILS_VERSION		RAILS_VERSION
README.rdoc		README.rdoc
RELEASING_RAILS.rdoc		RELEASING_RAILS.rdoc
Rakefile		Rakefile
install.rb		install.rb
load_paths.rb		load_paths.rb
rails.gemspec		rails.gemspec
version.rb		version.rb

Name		Name	Last commit message	Last commit date
actionmailer		actionmailer
actionpack		actionpack
activemodel		activemodel
activerecord		activerecord
activesupport		activesupport
ci		ci
railties		railties
tasks		tasks
tools		tools
.gitignore		.gitignore
.travis.yml		.travis.yml
.yardopts		.yardopts
Gemfile		Gemfile
RAILS_VERSION		RAILS_VERSION
README.rdoc		README.rdoc
RELEASING_RAILS.rdoc		RELEASING_RAILS.rdoc
Rakefile		Rakefile
install.rb		install.rb
load_paths.rb		load_paths.rb
rails.gemspec		rails.gemspec
version.rb		version.rb

Name		Name	Last commit message	Last commit date
actionmailer		actionmailer
actionpack		actionpack
activemodel		activemodel
activerecord		activerecord
activesupport		activesupport
ci		ci
railties		railties
tasks		tasks
tools		tools
.gitignore		.gitignore
.travis.yml		.travis.yml
.yardopts		.yardopts
Gemfile		Gemfile
RAILS_VERSION		RAILS_VERSION
README.rdoc		README.rdoc
RELEASING_RAILS.rdoc		RELEASING_RAILS.rdoc
Rakefile		Rakefile
install.rb		install.rb
load_paths.rb		load_paths.rb
rails.gemspec		rails.gemspec
version.rb		version.rb

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

About

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

About

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

About

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

About

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

About

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

About

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Uh oh!

Latest commit