Rails%203%20In%20Action

212 CHAPTER 8 More authorization
45 scenarios (45 passed)
451 steps (451 passed)
# and
26 examples, 0 failures, 11 pending
Everything’s still green, which means it’s time for another commit:
git add .
git commit -m "Added a seeds file"
git push
Now you’re done!
8.10 Summary
This chapter covered implementing authorization for your application and setting up
a permissions-based system for both the ProjectsController and TicketsController.
You started with a Permission model, which you used in a scope on the Project
model to show only the projects a user should be able to access. Then you used the
CanCan plugin, which provided the can? and cannot? methods to use first in the controllers
to stop users from accessing specified actions and then in the views, through
the authorized? method, to stop users from seeing specified links.
You implemented a way for admins to change the permissions of a user through
the admin backend of the system by displaying a series of check boxes. Here you used
an update action that wasn’t quite like the normal update action, and you had to
define a custom-named route for it.
Finally, you learned how to set up seed data for your application so you have a solid
base of objects to work from. Without using seed data, you’d have to manually set up
the data not only for your local development environment but also for your production
server, which can be tedious. Seed data saves you that effort. You also wrote a test
for this data in the form of a feature that ensures the data from the seed file is always
created when the seed task is run.
In chapter 9, you learn how to attach files to tickets. File uploading is an essential
part of any ticket-tracking application because files can provide that additional piece of
context required for a ticket, such as a screenshot, a patch, or any type of file. You also
learn about restricting the availability of these files on the basis of users’ permissions.