Added ability to unset conf_bind and listen on all interfaces.
Merge pull request #25 from simpleweb/conf-bind-optional

Allow conf_bind to be unset
New release for Forge
This commit adds a 'system_sysctl' parameter to Redis class.
This parameter is disabled (false) by default, but when enabled
sets the vm.overcommit_memory=1 sysctl setting on the Linux server.
In order to set this sysctl setting the sysctl module must be available.
The sysctl module required dependency was added to the Modulefile file.

The README.md file was updated to state how to use the 'system_sysctl'
parameter.

Some grammar changes.
Merge pull request #26 from tehmaspc/tehmaspc_add_sysctl_overcommit

system_sysctl parameter for redis class; handles setting vm.overcommit_memory via 'sysctl' puppet module.
Forge Release 0.0.11
Typo on tests/init.pp
Clean up use of 'UNSET' string

In Puppet, the `undef` keyword evaluates to boolean false. Thus, allows
for more concise code when evaluating to see if a variable exists or
not.

This commit will use the `undef` keyword in place of the string 'UNSET'.
It also prefers simple conditional expressions over string comparisons
in both the `::redis` class and the erb templates.
Use Redis bind default as parameter default value

By default, Redis will attempt to listen on all interfaces available on
a node. However, the `::redis` class currently uses restrictive default
parameters that do not operate as a default Redis installation is
expected to.

This commit uses 0.0.0.0 as the default bind address to replicate the
default equivalent of Redis. It also no long allows the bind directive to
be absent since the default behavior is equivalent to removing the bind
directive.

Generally speaking, this is a better best practice for module design. It
imposes less policy on the people who will be using the module and
leaves it as an exercise for them at implementation time.
Merge pull request #27 from trlinkin/unset_cleanup

Unset cleanup
Fixes #28
New Forge Release 0.0.12
Explaining the custom parameters
Changed operating system check to validate osfamily

Due to the large number of RHEL clones changed the operating system
check to look at osfamily rather than operatingsystem facts. Also did
the same for debian to be consistant.

For instance on Scientific Linux you would get the following somewhat
confusing error.

Unsupported osfamily: RedHat operatingsystem: Scientific, module redis
only support osfamily RedHat and Debian
trying a fix for librarian-puppet
fixing librarian-puppet dependency error
Merge pull request #29 from george-b/osfamily

Changed operating system check to validate osfamily
add unixsocket support for RHEL
octal modes should be quoted
Merge pull request #33 from oxilion/unixsocketoptions

Unixsocketoptions