file_system
file_system copied to clipboard
falood
Filesystem monitor for elixir
When deploying an application to Kubernetes, it's a good practice to configure the filesystem as read only, for security reasons (the filesystem can still be modified outside the container, for...
This, e.g., allows to monitor busy directories, such as `/dev` only for file creation/destruction. By default it will continue to act as if `events: [:modified, :moved_to, :moved_from, :created, :deleted, :attribute]`...
Is there a way to reliably and safely kill a FileSystem worker and its port?
Hi @falood, I am trying to use this package from another package (exsync) and keep getting this error message in my console: ``` 16:54:02.170 [error] Can't find executable `mac_listener` ```...
I have code like the following to watch two directories. I only care about getting a notification when the directory is updated. For my use-case, I don't care about receiving...
Some applications can change a file with many :modified/[:modified, :closed] But it's a good idea to process events only once (for example, at the end of file changes). It was...
Longterm goal: it would be nice to define a consistent API from all the backends. https://docs.google.com/document/d/1-GQrFdDVrA57-ce0kbzSth4lQqfOMMRKpih3hPJmvoU/edit might be a good starting place for research. /cc @whitfin
fs_poll should be available in the {:unix, :sunos} environment.
The linux backend calls it `:deleted` where as the macos backend calls it `:removed`. Should it not be consistent across the library, irrespective of the OS? --- [1] https://github.com/falood/file_system/blob/dc8f7d6cd7cfd492ebff7a53a58800c213d457bb/lib/file_system/backends/fs_inotify.ex#L59 [2]...
