Fixes #11413 - disable SQL logging by default

Fixes #10736 - Add permission specific logger

fixes #10711 - move LDAP logging to a separate logger

Fixes #10487: Add custom logging support

This change moves away from the Rails logger to the 'logging' gem
to support more configurability of logging. Further, this allows for
the creation of custom loggers that plugins can then create during
registration (with `logger`) or through settings....

Fixes #9606 - ANSI color codes should not be used in production log

Fixes #9059 - adds puppetssldir setting

fixes #3946 Set host URLs from local settings file, if no Facter configuration exists. Add default values for settings example.

Feature #2368 - i18n extracting strings

refs #2069 - enable auth by default

Without authentication, sensitive information and power is available to all,
so improve security out of the box.

fixes #1994 - set vardir for puppet 3, use --configprint

When running Puppet 3 as a non-root user (i.e. foreman), both --confdir and
--vardir have to be specified as per Puppet #16637, else SSL settings dependent
on vardir will fail.

This adds a new puppetvardir setting used with puppetconfdir, and supports...

Add organization and location to foreman.

This feature allows foreman to provide multi location, multi tenant and
multi organizations capablities.

the idea is that resources within foreman (e.g. hosts, subnets, users,
environments etc) can belong to one or more locations and organization,...

fixes #1961 Adding JSONP support

When using cross-domain requests, it is impossible to read the response
data, and process it.
Using JSONP allows a client, from a specific domain (for example
/domain1), to query data in another doamin (/domain2), and analyze it,...

Removed deprecated settings for settings.yaml.example

fixes #1188 - add a sample configuration file