We *very* much need to improve the documentation here, but you need to:
copy config/settings.yml.example to config/settings.yml
* set up a certificate/key for Dashboard so it can communicate over the API to the filebucket. This is probably easiest done with "puppet cert generate ...." on your CA then copying the files across to your Dashboard (assuming they're on different machines)
* fill in all the SSL cert/key settings in settings.yml
* fill in the file_bucket_server address in settings.yml
* set use_file_bucket_diffs: true in settings.yml
On your puppet master, make sure you have a filebucket 'main' defined, and that it's applying to all File resources. The easiest way is to put something like this in site.pp
filebucket { "main": server => "debian5-1.localdomain", path => false }
File { backup => "main" }
This sets the server for filebucket to "debian..." (replace with your server) and sets a resource default so all File resources use this filebucket.
Then when you run on your nodes, they'll backup file changes to the filebucket, and when they send reports to the dashboard, the md5{} checksums will be links to the filebucket.
As soon as you've got this working you're going to get frustrated by:
where we don't actually show the diff, just the old and new files. This should be a relatively easy fix to implement, as we have the complete API for showing diffs as per:
and we know the md5 to diff with.
Thanks
- Trey
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.