Skip to content
A Chef cookbook for the Python Watcher daemon.
Ruby
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
attributes
providers
recipes
resources
templates/default
CHANGELOG.md
LICENSE
README.md
metadata.rb

README.md

watcher Cookbook

This cookbook installs and configures the Python Watcher daemon (https://github.com/greggoryhz/Watcher), which uses the inotify kernel subsystem to monitor for file system changes and perform arbitrary actions.

Requirements

Platform

  • Red Hat, CentOS - I will be working on Debian support as I have a system that needs it!

cookbooks

  • git - needed to clone the latest version of the tool.
  • python - required for installing python dependencies and to execute the tool.

Attributes

watcher::default

Key Type Description Default
['watcher']['repo_url'] String The Git repository to clone the daemon from. https://github.com/greggoryhz/Watcher.git
['watcher']['branch'] String The branch or commit to checkout and use. master
['watcher']['install_path'] String Destination for the cloned tool. /usr/local/watcher
['watcher']['jobs'] Array A set of jobs for the Watcher daemon to manage. []

Usage

watcher::default

e.g. Just include watcher in your node's run_list:

{
  "name":"my_node",
  "run_list": [
    "recipe[watcher]"
  ]
}

Resources/Providers

This cookbook's resources are for other cookbooks to manage jobs for the daemon.

job

Manage jobs on the server.

Actions

  • :create: create a job

Attribute Parameters

  • name: name attribute. Name of the job.
  • label: description of the task.
  • path: file system path to monitor.
  • exclude: an array of sub-directories to ignore.
  • monitor: file system events to monitor (create, move_to, delete, etc.).
  • recursive: should the path be monitored recursively?
  • command: the command to be executed following a detected event.

Contributing

  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  3. Write your change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request using Github

License and Authors

Authors: Peter Green

You can’t perform that action at this time.