PCC: use settings.yml instead of hardcoding

[ndushay]

we have a branch (show-action-naomi) with a clear need for some settings so this can be set up off that branch (or master, if PR #25 is merged)

e.g. need config/settings.yml with values to be used by config/application.rb

We want to do the same sort of configuration approach we use in most rails apps, with the config gem and config/settings.yml with defaults and config/settings/[env].yml also with defaults, with no sensitive info in config/settings/production.yml. dlme project might be a good example.

This will set us up for #4, where we put VM specific or sensitive information into shared_configs and hook it up so rails app finds it as if it was in config/settings/[env].yml