› Build::Files::Monitor

Build::Files::Monitor

Efficiently monitor the filesystem for changes.

Development Status

Usage

Please browse the source code index or refer to the guides below.

Getting Started

This guide explains how to use build-files-monitor to efficiently monitor the filesystem for changes.

Releases

Please browse the releases for more details.

v0.4.0

  • Use io-watch for filesystem monitoring.

v0.3.0

  • Internal refactoring.

v0.2.1

  • Fixed compatibility of keyword arguments in Monitor.new to properly forward both positional and keyword arguments.

v0.2.0

  • Moved State class to build-files gem. Users should now require 'build/files/state' instead of require 'build/files/monitor/state'.

v0.1.0

  • Initial release.
  • Support for filesystem monitoring with platform-specific implementations (Build::Files::Monitor::Native using FSEvent/INotify).
  • Fallback polling implementation (Build::Files::Monitor::Polling).

Contributing

We welcome contributions to this project.

  1. Fork it.
  2. Create your feature branch (git checkout -b my-new-feature).
  3. Commit your changes (git commit -am 'Add some feature').
  4. Push to the branch (git push origin my-new-feature).
  5. Create new Pull Request.

Developer Certificate of Origin

In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.

Community Guidelines

This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.