敏捷Web开发：Rails实战与进阶

Ruby

Rails

需积分: 3 116 浏览量更新于2024-07-31 收藏 6.61MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"Agile Web Development 是一本关于使用Rails进行Web开发的入门书籍，由一家专注于Rails开发的公司推荐。本书适用于敏捷开发人员，目前处于Beta阶段，即在正式出版前的初步发布版本。读者可以提前几个月获取内容，并提供反馈以帮助改进书本。然而，由于尚未进行全面的技术编辑、复制编辑和布局设计，书中可能存在错误、错别字、格式问题等。尽管如此，作者相信读者仍能从中受益。你可以通过访问http://pragprog.com下载更新的电子版，直到书本完成。" 在这本名为“Agile Web Development”的书中，核心知识点围绕着使用Ruby on Rails框架进行敏捷Web开发。Rails是一个流行的开源Web应用程序框架，它基于Ruby编程语言，旨在简化和加速Web开发过程。以下是几个关键知识点： 1. **Ruby基础知识**：在深入学习Rails之前，了解Ruby语言的基本语法、数据类型、控制结构以及面向对象编程的概念是必要的。 2. **Rails架构**：Rails遵循MVC（模型-视图-控制器）架构，这使得代码组织有序且易于维护。理解模型如何代表数据，视图如何展示数据，以及控制器如何协调它们之间的交互至关重要。 3. **ActiveRecord**：这是Rails中的ORM（对象关系映射）工具，它允许开发者用Ruby代码操作数据库，减少了直接编写SQL的需要。 4. **路由**：Rails的路由系统将URL映射到控制器方法，理解如何配置和使用路由规则对于构建动态和可扩展的Web应用至关重要。 5. **敏捷开发原则**：这本书强调了敏捷开发方法，包括迭代开发、用户故事、持续集成、测试驱动开发(TDD)和重构等实践，这些都是提高开发效率和软件质量的关键。 6. **TDD与集成测试**：测试驱动开发是敏捷开发的核心部分，书中会介绍如何编写测试用例，以及如何利用RSpec或MiniTest等工具进行单元测试和集成测试。 7. **Gem和依赖管理**：Rails应用通常依赖于许多第三方库，称为Gems。了解如何管理和使用Gemfile来管理这些依赖关系对于开发过程是重要的。 8. **Rails生成器和命令行工具**：Rails提供了许多命令行工具，如`rails new`创建新项目，`generate`生成模型、控制器等，学习这些工具可以加速开发流程。 9. **安全性和最佳实践**：书中可能会涵盖防止SQL注入、XSS攻击、CSRF等安全问题，以及遵循最佳实践来确保代码健壮和可维护。 10. **部署与持续集成**：了解如何将Rails应用部署到生产环境，如Heroku或AWS，并设置持续集成服务如Jenkins或CircleCI以自动化测试和部署。随着本书的逐步完善，读者将能够获取最新的版本，获得更完整和精确的信息。尽管此Beta版可能存在一些瑕疵，但它提供了宝贵的早期学习机会，让开发者可以紧跟Rails和敏捷开发的最新趋势。

资源详情

资源推荐

Acknowledgements

You’d think that producing a new edition of a book would be easy. After all,

you already have all the text. It’s just a tweak to some code here and a minor

wording change there, and you’re done. You’d think....

It’s difﬁcult to tell exactly, but our impression is that creating each edition

of Agile Web Development with Rails took about as much effort as the ﬁrst

edition. Rails is constantly evolving and, as it does, so has this book. Parts

of the Depot application were rewritten several times, and all of t he narrative

was updated. The emphasis on REST and the avoidance of features as they

become deprecated have repeatedly changed the structure of the book as what

was once hot became just lukewarm.

So, this book would not exist without a massive amount of help from the

Ruby and Rails communities. Each edition of this book has been r eleased as

a beta book: early versions wer e posted as PDFs, and people made comments

online. And comment they did: more than 1,200 suggestions and bug reports

were posted. The vast majority ended up being incorporated, making this book

immeasurably more useful than it would have been. Thank you all, both for

supporting the beta book program and for contributing so much valuable

feedback.

The Rails core team has been incredibly helpful, answering questions, check-

ing out code fragments, and ﬁxing bugs. A big thank you to the following:

Scott Barron (htonl), Jamis Buck (minam), Thomas Fuchs (madrobby),

Jeremy Kemper (bitsweat), Yehuda Katz (wycats),

Michael Koziarski (nzkoz), Marcel Molina Jr, (noradio),

Rick Olson (technoweenie), Nicholas Seckar (Ulysses),

Sam Stephenson (sam), Tobias Lütke (xal), José Valim (josevalim), and

Florian Weber (csshsh)

We’d like to t hank the folks who contributed the specialized chapters to the

book: Leon Breedt, Mike Clark, James Duncan Davidson, Justin Gehtland,

and Andreas Schwarz.

Prepared exclusively for Anton Fonarev

RAILS SIMPLY FEELS RIGHT 19

Rails applications are written in Ruby, a modern, object-oriented scripting

language. Ruby is c oncise without being unintelligibly terse—you can express

ideas naturally and cleanly in Ruby code. This leads to pr ogra ms that are easy

to write and (just as important) are easy to read months later.

Rails takes Ruby to the limit, extending it in novel ways that make a pro-

grammer’s life easier. This makes our programs shorter and more readable.

It also allows us to perform tasks that would normally be done in external

conﬁguration ﬁles inside the codebase instead. This makes it far easier to see

what’s happening. The following code deﬁnes t he model class for a project.

Don’t worry about the details for now. Instead, just think about how much

information is being expressed in a few lines of code.

class Project < ActiveRecord::Base

belongs_to :portfolio

has_one :project_manager

has_many :milestones

has_many :deliverables, :through => :milestones

validates :name, :description, :presence => true

validates :non_disclosure_agreement, :acceptance => true

validates :short_name, :uniqueness => true

end

Two other philosophical underpinnings keep Rails code short and readable:

DRY and convention over conﬁguration. DRY stands for don’t repeat yourself :

every piece of knowledge in a system should be expressed in just one place.

Rails uses the power of Ruby to bring that to life. You’ll ﬁnd very little duplica-

tion in a Rails application; you say what you need to say in one place—a place

often suggested by the conventions of the MVC architecture—and then move

on. For programmers used to other web frameworks, where a simple change

to the schema could involve them in half a dozen or more code changes, this

was a revelation.

Convention over conﬁguration is cr ucial, too. It means that Rails has sensi-

ble defaults for just about every aspect of knitting together your application.

Follow the conventions, and you can write a Rails application using less code

than a ty pical Java web application uses in XML conﬁguration. If you need to

override the conventions, Rails makes that easy, too.

Developers coming to Rails found something else, too. Rails isn’t playing catch-

up with the new de facto web standards; it’s helping deﬁne them. And Rails

makes it easy for developers to integrate features such as Ajax and RESTful

interfaces into their code, because support is built in. (And if you’re not famil-

iar with Ajax and REST interfaces, never fear—we’ll explain them later in the

book.)

Report erratum

this copy is (B10.0 printing, October 28, 2010)

Prepared exclusively for Anton Fonarev

RAILS IS AGILE 20

Developers are worried about deployment, too. They found that with Rails you

can deploy successive releases of your application to any number of servers

with a single command (and roll them back equally easily should the release

prove to be somewhat less than perfect).

Rails was extracted from a real-world, commercial application. It turns out

that the best way to create a framework is to ﬁnd the central themes in a

speciﬁc application and then bottle them up in a generic foundation of code.

When you’re developing your Rails application, you’re starting with half of a

really good application already in place.

But there’s something else to Rails—something that’s hard t o describe. Some-

how, it just feels right. Of course, you’ll have to take our word for that until

you write some Rails applications for yourself (which should be in the next 45

minutes or so...). That’s what this book is all about.

Rails Is Ag il e

The title of this book is Agile Web Development with Rails. You may be sur-

prised to discover that we don’t have explicit sections on applying agile prac-

tices X, Y, and Z to Rails coding.

The reason is both simple and subtle. Agility is part of the fabric of Rails.

Let’s look at the v alues expressed in the Agile Manifesto as a set of four pref-

erences:

• Individuals and interactions over processes and t ools

• Working software over comprehensive documentation

• Customer collaboration over contract negotiation

• Responding to change over following a plan

Rails is all about individuals and interactions. There are no heavy toolsets,

no complex conﬁgurations, and no elaborate processes. Ther e ar e just small

groups of developers, their favorite editors, and chunks of Ruby code. This

leads to transparency; what the developers do is reﬂected immediately in what

the customer sees. It’s an intrinsically interactive process.

Rails doesn’t denounce documentation. Rails makes it trivially easy to cre-

ate HTML documentation for your entire codebase. But the Rails development

process isn’t driven by documents. You won’t ﬁnd 500-page speciﬁcations at

the heart of a Rails project. Instead, you’ll ﬁnd a group of users and devel-

opers jointly exploring their need and the possible ways of answering that

need. You’ll ﬁnd solutions that change as both the developers and the users

become more experienced with the problems they’re trying to solve. You’ll ﬁnd

1. http://agilemanifesto.org/. Dave Thomas was one of the seventeen authors of this document.

Report erratum

this copy is (B10.0 printing, October 28, 2010)

Prepared exclusively for Anton Fonarev

剩余471页未读，继续阅读

hkfwy

粉丝: 0
资源: 2

敏捷Web开发：Rails实战与进阶

Agile Web Development with Rails

Agile Web Development With Ruby On Rails第一及第二版

Test-Driven Development

agile_modbusrtu

agile 和scrum的关系

iterative model

qca芯片Agile模式开启不了

agile 9.3.1.2

agile java

Agile Controller-Campus 下载

agile controller

python系统需求规格说明书参考文献

What are the most significant differences among structured, object-oriented, and agile methods? What do they have in common?

agile modbus教程

agile_modbus

推荐的代码规范学习资料

安装Agile controller

单一职责原则是从哪个概念演化来的

rtt agile_modbus

最新资源