Update attributes to match margarine's parameters.
Remove metadata.json.

Generated files shouldn't be kept in version control.  They should be
generated when needed or as part of a build and deploy process.
Add attributes to indicate margarine components.

Attributes have been added that indicate if particular components of
margarine have been installed.
Add box for all-in-one installation.
Remove newline from Berksfile.
Add chef-solo-search to berks for data_bags.
Add data_bag items for log handling.
Add data_bags and chef-solo-search to vagrant.
Fix JSON problems in data_bags.
Add housekeeping attributes for margarine.

Add attributes specifying the user and group for margarine as well as
whether syslog should be included as the logging mechanism.
Group service level items into a category.
Remove automatic cookbooks.

Berks seems to pull in dependencies of dependencies automatically but
some things may need to be added back in.  I'm not well-versed in
berks-fu yet.
Simplify default recipe.

The default recipe should be perfect for creating a demo application and
as such doesn't need to do anything besides call the component cookbooks
and set appropriate demo attributes.
Simplify component cookbooks.

The components (tinge, blend and spread) should be broken into
components so that common portions are kept DRY.  Thus, each component
cookbook simply sets its attribute and then installs, configures, and
starts services.
Add installation recipes.

I've broken the installation recipe into several different recipes:

:install: Default installation recipe.  Calls the others as appropraite.

.. note::
  The rest of these recipe descriptions drop the leading install_

:package: Use normal package mechanisms to install margarine.
:pip:     Use pip to install margarine.
:source:  Install margarine from source using git deploy.

The install_source_dependencies recipe has been split out so that it
might be called separately if required.  Such as by another project's
(margarine) Vagrantfile thus bypassing the rest of the installation.
Add configuration recipes.

The configuration recipes take care of the various configuration
directories and files.  These files are logging.ini, margarine.ini, and
pyrax.ini.

The two added recipes take care of crafting the above templates for
configuration.
Add use and group recipes.
Remove replaced templates for configuration.
Add hepler library for templates.

The margarine.ini template uses a uri helper function to simplify
creation of the URIs in that file.
Update attribute definitions.

The attributes should be in a fairly complete form at this point but
some aren't used and some still need to be added.

Notably, margarine.install.version needs to be added and udpated in
recipes accordingly.