In order to prevent users from passing in configuration key/values pairs through the $config hash parameter that already exist hardcoded in the template we should move all these hardcoded values into the $config_defaults hash so merging happens correctly and duplicates don't happen.

This package should by default utilize the chocolatey package from the community feed along with giving the user the flexibility to customize to their internal feed for production scenarios.

RavenDB Exposes a restful API. Lets see what we can come up with in order to be able to manage ravendb databases utilizing it's rest API using types and providers. Before i can do this i need to play around with the following.

Look at a couple of modules to see how they organize helper methods and stuff that make the actual rest apis

Methods of possibly reusing a gem

• Test a simple rake task that will grab a gem or git repo that contains the rest api library and massage it into this module for use. or just traight up vendor the gem in a folder somewhere in the lib directory.
• Test Git submodules for reusing a rest api library
• Test installing the gem on the target system using puppet_gem

Looks like service_manage is missing from documentation readme.

I made a copy paste at the following location and need to correct this.

Since this is a database you might not want to restart the service by puppet when a configuration file change happens. We should implement an option to allow this to be configurable.

In order to keep this module easy to use i want to leave the RavenDB port as a seperate parameter outside the config hash even though i will ultimately merge it in from within the config class. I need to put a protection in place that will prevent the user from using the module possibly incorrectly by preventing them from passing the ravendb port into the config hash. It looks like i can use this from the stdlib to achieve this.

https://github.com/puppetlabs/puppetlabs-stdlib#has_key

I released this to the forge but forgot i needed to actually update the documentation. I should do this for next release.

Before i did a bit of a hack to inject in line endings to my ERB template. I should probably using something more formal like the below OR just save the file with the correct line endings.

Option 1:
https://github.com/puppetlabs/puppetlabs-stdlib#unix2dos
https://github.com/puppetlabs/puppetlabs-stdlib#dos2unix

Option 2:
Save file with correct line endings

We need to implement a way for the client to pass in key value pais that can be placed correctly into the ravendb configuration file. Currently values are hardcoded to the default after install.

https://github.com/TraGicCode/tragiccode-ravendb/blob/master/templates/Raven.Server.exe.config.epp