Make links in docs index relative, for github karma.
Update api.md
Update node.md
put it back and add hint info
Merge pull request #5 from mikeyp-dell/master

+2 Make links in docs index relative, for github karma.
Add missing node_role_datum model.

Somehow, this file got left out of the last set of merges Rob made from
the old repo structure, and its absence was breaking the scaffolds.
Get rid of unneeded random number for node_roles.

This was causing schema.rb to be regenerated on every run, which in turn
caused unneeded VCS churn.
Fix the Crowbar init script to run Crowbar with the right env.

All commands that act on or for the Crowbar framework need to run in a
login session as the crowbar user to ensure that the right ruby env is
being used if we are not using the system ruby.
Fix the Crowbar CLI to run in Rails 1.8.7

Sigh, in 1.8.7 "foo"[0] gives you a number instead of a string of length 1
Use FHS compliant paths for the Gem installs.

/var/run is likely to be nuked without notice.
Zap some unneeded packages from the crowbar.yml

This strips out everything that is not strictly required to bootstrap Ubuntu.
Switch to having in_docker use opencrowbar base images.
On Centos, Install ruby 2.0.0 using RVM.

This installs ruby 2.0.0 to the crowbar user account on CentOS 6.5,
letting us use a modern Rails for the Crowbar web app on without
screwing up the system ruby.
Fix up the bootstrap recipe to let Centos work

This also changes things to use more FHS compliant paths.
Change where simplecov puts its test coverage.

We may want to drop this patch.
Clean whitespace in development config file
Fix up crowbar.yml for centos builds.

This shifts the required package list around to make bootstrapping pull
in the packages needed to let the framework run on Centos.
Change which migration-generated files we track.

Added are the delayed_jobs and rails_settings created files, as they are
not likely to change until we pull in a newer version of the gem.

Gone is rails/db/schema.rb, because it is likely to grow more sections
as we start doing builds with workloads, and I do not think the
cognitive overhead for tracking when it shold be committed vs. when it
should be ignored is worth it.

This also consolidates the .gitignore files.