JSON encode values embedded in the salt-master's configuration file

repo.saltstack.com handles all currently supported Debian releases as well
as all supported Ubuntu releases so this change should be fine.

Part of #180.

This avoids problems when values are strings containing colons. And it
mimicks what was already done for the salt-minion's configuration file.

Fixes #233.

Lxcprofile

GitPython package name is fixed for RedHat-based OS

Fixing GitPython package name for RedHat OS family. Tested on CentOS 7.

Render config as JSON

Support engine configuration

Add support for master eauth LDAP config

Ability to create non-templated cloud maps/providers/profiles

allow gitfs.keys state to function without error when no keys

add new gitfs functionality

Use the latest stable salt from repo.saltstack.com

Comment out second master config example

This second master config example was causing problems when vagrant
would use the default pillar.example

Added version check for provider/driver backwards compatibility

Renamed "provider" to "driver"

Prefix configuration files with the suitable O/S-specific pathname

Without this change, importing map.jinja in config files (as opposed to
SLS files) causes a rendering error because `slspath` isn't defined.
The `salt_settings.key_url` variable gets used only in
`salt/pkgrepo/debian/init.sls`.

add formula file this fixes #211

Take mine_functions back

Add Windows support to map.jinja

This adds some minimal support for Windows minions.

Fix Windows repo settings using values from 2015.8 documentation

update 2015.8.7 version config for the minion

merge options from 2015.8.7 version in f_defaults.conf

Revert PR #200

This restores the original structure/behavior of the
`salt_formulas` Pillar key.