Rails%203%20In%20Action

to this:
Seed data
def permissions
{
"view" => "View",
"create tickets" => "Create Tickets",
"edit tickets" => "Edit Tickets",
"delete tickets" => "Delete Tickets"
}
end
By adding these two permissions here, you display the check boxes that should make
your scenarios all green. Let’s run the feature with bin/cucumber features/assigning
_permissions.feature to find out:
4 scenarios (4 passed)
72 steps (72 passed)
How great are you? Two features with one blow. Awesome stuff.
That’s the final piece of the authorization puzzle. You now have a way for admins
to assign permissions to users. But does everything work? Here’s hoping! Let’s run
rake cucumber:ok spec:
44 scenarios (44 passed)
448 steps (448 passed)
# and
26 examples, 0 failures, 11 pending
Awesome! Let’s commit this:
git add .
git commit -m "Added creating, editing, updating and deleting
tickets to assigning permissions interface"
git push
Although it’s great that you now have an interface for assigning permissions, you
don’t have a way to do it without first having an admin user set up. You can set up an
admin user manually through the console, or you can do it by creating seed data.
8.9 Seed data
Seed data is records created for the purpose of providing the minimal viable requirements
to get an application running. Before Rails 2.2, many applications implemented
such records through using plugins such as seed_fu, but since 2.2, seed data is
built in.
Seed data allows you to create records for your application to provide a usable base
if you or anybody else wants to get set up with the application quickly and easily. For
your application’s seed data, you’ll create an admin user and an example project.
From there, anybody using the admin user will be able to perform all the functions of
the application.
Seed data lives under db/seeds.rb, and you can run this file by running rake
db:seed. The code for this rake task is this:
load Rails.root + "db/seeds.rb"
209