Rails%203%20In%20Action

450 CHAPTER 16 Basic performance enhancements
This time, rather than simply processing your action and sending the response body
back to the server, Rails will save the body in a new file in your application at public/
projects/1.html. The next time this route is requested, because the public/projects/
1.html page exists, it will be served by your web server, rather than Rails. A side-effect
of this means that your request will not show up in the Rails console, but at least it will
be served faster.
Let’s reload the page now; it should be a little faster because it’s serving that static
page. If you click the Next link on your pagination, you’ll still be shown the first page.
This is because the GET parameter was ignored, and the first page for this project’s
tickets was what was cached.
There’s another problem too: this result is cached for all users of your application.
At the top of the page, you’ll be able to see the message that says “Signed in as
admin@ticketee.com,” as shown in figure 16.6.
To see this little issue in action, sign up as another user by first clicking the Sign
Out link in the application to sign out, then the Sign Up link to be presented with a
form to sign up. In this form, enter user@ticketee.com for the email and password
for both the password and password confirmation fields. When you click the Sign Up
button, this will create your new user account.
You currently require users to confirm their account through an email they
receive, but because you’re in development mode there will be no emails sent. To confirm
this user, launch rails console now and run these commands:
user = User.find_by_email("user@ticketee.com")
user.confirm!
You’ll also need to give this user access to the first project in your system, so that they
can view the tickets too. To do this, run these couple of commands:
project = Project.first
user.permissions.create!(:action => "view", :thing => project)
Alright, now that your user is confirmed and has access to this project, let’s see what
happens when you sign in with the email and password you used to sign up,
user@ticketee.com and password. At the top of the page you’ll see that you’re signed
in as the new user, as seen in figure 16.7.
Figure 16.6 Signed in as admin Figure 16.7 Signed in as a user