#753 first user = superuser

[orenyk]

resolves #753

[orenyk]

The only thing I'm not sure about for this is whether or not this is actually a good idea. If we operate on the assumption that the person running rake app:setup will create a developer / devops account for themselves, rather than one of the usual admins, then this is safe. However, if they're just creating an account for an admin then we'll be giving that admin way too much power. Thoughts?

[orenyk]

check seed.rb

[coollog]

Should change the text when not set up from "Hey there! It looks like you haven't fully set up your application yet. To create your first admin user and configure the application, please run $bundle exec rake app:setup in the terminal. For more information, please see our github page: https://github.com/YaleSTC/reservations" to "... create your first super user and configure the application ..."

And the rake app:setup text "Welcome to reservations! Before using your application, we need to create an
initial administrator account and set some application-wide configurations.
This administrator account can be used later to create other admins, import
users, and change any configurations that you set from this script. With
that in mind, let's get started!

We need to start by creating an admin account. Please enter the
following info:"
to be about setting up the initial super user instead.

Otherwise, the first user created is a Super User as intended. Reviewed.

[orenyk]

Great catches, I'll get those prompts changed and then we can merge. Thanks!

[orenyk]

We had some weird bundle issues; we should start specifying versions in our Gemfile for stability anyway, so I fixed it by specifying the version of paper_trail (we've seen this error before). Now that we're green I'm merging this in :-)