Rails 4最佳实践指南

5星 · 超过95%的资源需积分: 10 132 浏览量更新于2024-07-24 收藏 3.55MB PDF 举报

"The Rails 4 Way" 是由 Obie Fernandez、Kevin Faustino 和 Vitaly Kushner 合著的一本专业书籍，于 2013 年 4 月 30 日发布。这是一本基于 Lean Publishing 过程的电子书，该过程允许作者和出版商通过轻量级工具进行迭代，并在编写过程中不断获取读者反馈，以确保最终产品能满足市场需求。这本书的初衷是提供关于 Ruby on Rails 4（简称 Rails 4）的深入理解和实践经验，适合那些想要了解最新框架技术的开发者。书中包含以下章节： 1. 序言 - 介绍了书籍的整体背景和作者对 Rails 4 的理解，以及为何选择这个主题进行深入探讨。 2. 致谢 - 感谢所有参与和支持本书创作的人。 3. 作者简介 - 作者们的背景介绍，包括他们在 Rails 开发领域的专业知识和经验。 4. 引言 (Beta 版) - 对 Rails 4 的简要介绍，强调了新版本的重要改进和核心理念。 5. 关于这本书 - 详细阐述了本书的目的、内容结构以及如何适应不断变化的开发环境。 6. 推荐阅读与资源 - 提供了其他相关书籍、文档和在线资源，帮助读者扩展学习路径。 7. 目标 - 阐明了读者通过阅读本书可以达到的技术能力和业务理解目标。 8. 前置知识 - 对读者需要具备的基础技能进行了概述，如 Ruby 编程基础和 Rails 概念。 9. 所需技术 - 明确列出读者在学习过程中应掌握或熟悉的技术工具，如 Git、RubyGems 等。本书将深入讲解 Rails 4 的各个方面，包括但不限于路由、模型-视图-控制器 (MVC) 设计模式、Active Record ORM、模板引擎、测试实践以及部署策略。随着 Rails 4 的发布，很多新特性被引入，如 Action Caching、Asset Pipeline 的优化和 Devise 登录系统等，使得这本书对于那些希望紧跟 Rails 技术发展的人来说具有很高的实用价值。作为一本 beta 版本的书籍，"The Rails 4 Way" 旨在鼓励读者参与到书的开发过程中，通过社交媒体分享和反馈，共同提升内容的质量和完整性。通过 Twitter 上的标签 #tr4w，读者可以发现更多关于这本书的讨论和评价。这是一本既实用又互动的指南，适合那些希望深入了解和掌握 Rails 4 开发的程序员，无论是初学者还是经验丰富的开发者，都能从中受益匪浅。

(Beta Version) Introduction vi

Sample Code and Listings

The domains chosen for the code samples should be familiar to almost all professional developers. They

include time and expense tracking, auctions, regional data management, and blogging applications. I don’t

spend pages explaining the subtler nuances of the business logic for the samples or justify design decisions

that don’t have a direct relationship to the topic at hand. Following in the footsteps of my series colleague Hal

Fulton and The Ruby Way, most of the snippets are not full code listings—only the relevant code is shown.

Ellipses (…) denote parts of the code that have been eliminated for clarity.

Whenever a code listing is large and significant, and I suspect that you might want to use it verbatim in your

own code, I supply a listing heading. There are not too many of those. The whole set of code listings will not

add up to a complete working system, nor are there 30 pages of sample application code in an appendix. The

code listings should serve as inspiration for your production-ready work, but keep in mind that it often lacks

touches necessary in real-world work. For example, examples of controller code are often missing pagination

and access control logic, because it would detract from the point being expressed.

Some of the source code for my examples can be found at http://github.com/obie/tr3w_time_and_expenses.

Note that it is not a working nor complete application. It just made sense at times to keep the code in the

context of an application and hopefully you might draw some inspiration from browsing it.

Concerning 3rd-Party RubyGems and Plugins

Whenever you find yourself writing code that feels like plumbing, by which I mean completely unrelated to

the business domain of your application, you’re probably doing too much work. I hope that you have this

book at your side when you encounter that feeling. There is almost always some new part of the Rails API or

a third-party RubyGem for doing exactly what you are trying to do.

As a matter of fact, part of what sets this book apart is that I never hesitate in calling out the availability of

third-party code, and I even document the RubyGems and plugins that I feel are most crucial for effective

Rails work. In cases where 3rd-party code is better than the built-in Rails functionality, we don’t cover the

built-in Rails functionality (pagination is a good example).

An average developer might see his productivity double with Rails, but I’ve seen serious Rails developers

achieve gains that are much, much higher. That’s because we follow the Don’t Repeat Yourself (DRY) principle

religiously, of which Don’t Reinvent The Wheel (DRTW) is a close corollary. Reimplementing something

when an existing implementation is good enough is an unnecessary waste of time that nevertheless can be

very tempting, since it’s such a joy to program in Ruby.

Ruby on Rails is actually a vast ecosystem of core code, official plugins, and third-party plugins. That

ecosystem has been exploding rapidly and provides all the raw technology you need to build even the most

complicated enterprise-class web applications. My goal is to equip you with enough knowledge that you’ll be

able to avoid continuously reinventing the wheel.

Recommended Reading and Resources

Readers may find it useful to read this book while referring to some of the excellent reference titles listed in

this section.

(Beta Version) Introduction vii

Most Ruby programmers always have their copy of the “Pickaxe” book nearby, Programming Ruby (ISBN:

0-9745140-5-5), because it is a good language reference. Readers interested in really understanding all of the

nuances of Ruby programming should acquire The Ruby Way, Second Edition (ISBN: 0-6723288-4-4).

I highly recommend Peepcode Screencasts, in-depth video presentations on a variety of Rails subjects by the

inimitable Geoffrey Grosenbach, available at http://peepcode.com

Ryan Bates does an excellent job explaining nuances of Rails development in his long-running series of free

webcasts available at http://railscasts.com/

Last, but not least, this book’s companion website at http://tr3w.com is the first place to look for reporting

issues and finding additional resources, as they become available.

Regarding David Heinemeier Hansson a.k.a. DHH I had the pleasure of establishing a friendship with David

Heinemeier Hansson, creator of Rails, in early 2005, before Rails hit the mainstream and he became an

International Web 2.0 Superstar. My friendship with David is a big factor in why I’m writing this book today.

David’s opinions and public statements shape the Rails world, which means he gets quoted a lot when we

discuss the nature of Rails and how to use it effectively.

David has told me on a couple of occasions that he hates the “DHH” moniker that people tend to use instead

of his long and difficult-to-spell full name. For that reason, in this book I try to always refer to him as “David”

instead of the ever-tempting “DHH.” When you encounter references to “David” without further qualification,

I’m referring to the one-and-only David Heinemeier Hansson.

There are a number of notable people from the Rails world that are also referred to on a first-name basis in

this book. Those include:

• Yehuda Katz

• Jamis Buck

• Xavier Noria

Goals

As already stated, I hope to make this your primary working reference for Ruby on Rails. I don’t really

expect too many people to read it through end to end unless they’re expanding their basic knowledge of

the Rails framework. Whatever the case may be, over time I hope this book gives you as an application

developer/programmer greater confidence in making design and implementation decisions while working on

your day-to-day tasks. After spending time with this book, your understanding of the fundamental concepts

of Rails coupled with hands-on experience should leave you feeling comfortable working on real-world Rails

projects, with real-world demands.

If you are in an architectural or development lead role, this book is not targeted to you, but should make you

feel more comfortable discussing the pros and cons of Ruby on Rails adoption and ways to extend Rails to

meet the particular needs of the project under your direction.

Finally, if you are a development manager, you should find the practical perspective of the book and our

coverage of testing and tools especially interesting, and hopefully get some insight into why your developers

are so excited about Ruby and Rails.

1 Rails Environments and Configuration

[Rails] gained a lot of its focus and appeal because I didn’t try to please people who didn’t share

my problems. Differentiating between production and development was a very real problem for

me, so I solved it the best way I knew how.

—David Heinemeier Hansson

Rails applications are preconfigured with three standard modes of operation: development, test, and pro-

duction. These modes are basically execution environments and have a collection of associated settings that

determine things such as which database to connect to, and whether the classes of your application should be

reloaded with each request. It is also simple to create your own custom environments if necessary.

The current environment can be specified via the environment variable RAILS_ENV, which names the desired

mode of operation and corresponds to an environment definition file in the config/environments folder.

You can also set the environment variable RACK_ENV or as a last resort you may rely on the default being

development. Since this environment setting governs some of the most fundamental aspects of Rails, such as

class loading, in order to really understand the Rails way you should understand its environment settings.

In this chapter, we start by covering Bundler, a tool that manages gem dependencies for your Ruby application.

It takes a gem manifest file and is able to fetch, download, and install the gems in the manifest, and all child

dependencies. Then we move on to how Rails starts up and handles requests, by examining scripts such as

boot.rb and application.rb and the settings that make up the three standard environment settings (modes).

We also cover some of the basics of defining your own environments, and why you might choose to do so.

Note that this book is not written with absolute newcomers to Rails in mind. To make the most out of this

book, you should already be at least somewhat familiar with how to bootstrap a Rails application and the

meaning of M.V.C. If you are not, I recommend that you first take advantage of the excellent Ruby on Rails

Tutorial website¹ by Michael Hartl, another Professional Ruby Series author.

1.1 Bundler

Bundler² is not a technology that is specific to Rails 4, but it is the preferred way to manage your application’s

gem dependencies. Applications generated with Rails 4 use Bundler automatically, and you should not need

to install the bundler gem separately since it’s a dependency of Rails 3 itself.

Since we believe that you should use Bundler, figuring out how to not use Bundler is left as an exercise for

adventurous and/or nonconformist readers.

One of the most important things that Bundler does is dependency resolution on the full list of gems specified

in your configuration, all at once. This differs from the one-at-a-time dependency resolution approach

employed by Rubygems and previous versions of Rails, which can (and often did) result in the following

hard-to-fix problem:

¹http://railstutorial.org

²http://gembundler.com

剩余680页未读，继续阅读

BoyishWei

粉丝: 3
资源: 1

Rails 4最佳实践指南

The Rails 5 Way(4th) 无水印原版pdf

The Rails 4 Way

THE RAILS 4 WAY, 3RD EDITION

The Rails 4 Way, 3rd edition.pdf

Obie Fernandez, Kevin Faustino, Vitaly Kushner - The Rails 4 Way - 2014

The Rails 4 Way: 实战指南（2013年最新版）

The Rails 5 way 英文原版

the rails way

The Rails Way

The rails way

最新资源