Chapter 1. Ruby on Rails, the framework
1.2. Developing your first application
1.2.2. Generating an application
1.2.3. Starting the application
Chapter 2. Testing saves your bacon
2.1. Test- and behavior-driven development
2.3. Behavior-driven development
Chapter 3. Developing a real Rails application
5.1.2. Creating a tickets controller
5.1.3. Defining a has_many association
5.1.4. Creating tickets within a project
Chapter 6. Authentication and basic authorization
6.3. Confirmation link sign-in
6.5.1. Attributing tickets to users
6.5.3. Fixing the Viewing Tickets feature
Chapter 7. Basic access control
7.1. Projects can be created only by admins
7.2. Adding the admin field to the users table
7.3. Restricting actions to admins only
7.3.1. Fixing three more broken scenarios
8.3.1. Fixing Editing Projects
8.4. Blocking access to tickets
8.6. Restricting update access
8.7. Restricting delete access
9.1.1. A feature featuring files
9.3. Serving files through a controller
9.4.3. Adding more files with JavaScript
10.2. Changing a ticket’s state
12.1. Sending ticket notifications
12.1.1. Automatically watching a ticket
12.1.3. Defining the watchers association
12.1.4. Introducing Action Mailer
12.2.1. Testing comment subscription
12.3.1. Testing real-world email
13.2. Beginning the tickets API
14.3. Creating a user for the app
14.5.2. Configuring Capistrano
14.5.3. Setting up the deploy environment
Chapter 15. Alternative authentication
15.2.2. Registering an application with Twitter
Chapter 16. Basic performance enhancements
16.2. Database query enhancements
17.1. A brief history of engines
17.4. Setting up a testing environment
17.5. Writing your first engine feature
17.6. Adding more posts to topics
17.7. Classes outside your control
Chapter 18. Rack-based applications
18.1. Building Rack applications
18.2. Building bigger Rack applications
18.3. Mounting a Rack application with Rails
A.1 Reason #1: the sense of community
3.14.131.212