The steeloverseer package

[Tags:bsd3, library, program, test]

A command line tool that responds to filesystem events. Allows the user to automatically execute commands after files are added or updated. Watches files using regular expressions.


[Skip to Readme]

Properties

Versions 0.1.0.1, 0.1.0.2, 0.2.0.0, 0.5.0.0, 0.5.0.1, 1.0.1.0, 1.1.0.0, 1.1.0.1, 1.1.0.2, 1.1.0.3, 1.1.0.4, 1.1.0.5, 1.1.0.6, 1.1.1.0, 2.0, 2.0.0.1, 2.0.1.0
Dependencies aeson (>=0.8), ansi-terminal (>=0.6.2), async (>=2.0), base (>=4.0 && <5.0), bytestring (>=0.10), containers (>=0.5), directory (>=1.2), filepath (>=1.3), fsnotify (>=0.2), hfsevents (>=0.1.3), mtl (>=2.2), optparse-applicative (>=0.11), process (>=1.2), regex-tdfa (>=1.2), resourcet (>=1.0), semigroups (>=0.16), steeloverseer, stm (>=2.4), streaming (>=0.1.0 && <0.1.5), text (>=1.2), yaml (>=0.8) [details]
License BSD3
Author Schell Scivally, Mitchell Rosen
Maintainer efsubenovex@gmail.com
Category Development
Home page https://github.com/schell/steeloverseer#readme
Bug tracker https://github.com/schell/steeloverseer/issues
Source repository head: git clone https://github.com/schell/steeloverseer
Uploaded Wed Feb 1 18:10:47 UTC 2017 by SchellScivally
Distributions NixOS:2.0.1.0
Downloads 2463 total (132 in the last 30 days)
Votes
2 []
Status Docs available [build log]
Last success reported on 2017-02-01 [all 1 reports]
Hackage Matrix CI

Modules

[Index]

Downloads

Maintainer's Corner

For package maintainers and hackage trustees

Readme for steeloverseer

Readme for steeloverseer-2.0.1.0

Steel Overseer

A file watcher and development tool, similar to Ruby's Guard.

Build Status

Installation

Download and install the stack build tool.

stack install steeloverseer

This will create a binary deep inside ~/.stack/, and symlink to it at ~/.local/bin/sos.

Usage

See sos --help to get started:

Steel Overseer 2.0.1

Usage: sos [TARGET] [--rcfile ARG] [-c|--command COMMAND] [-p|--pattern PATTERN]
  A file watcher and development tool.

Available options:
  -h,--help                Show this help text
  TARGET                   Optional file or directory to watch for
                           changes. (default: ".")
  --rcfile ARG             Optional rcfile to read patterns and commands
                           from. (default: ".sosrc")
  -c,--command COMMAND     Add command to run on file event.
  -p,--pattern PATTERN     Add pattern to match on file path. Only relevant if
                           the target is a directory. (default: .*)

Patterns and Commands

Capture groups can be created with ( ) and captured variables can be referred to with \1, \2, etc. (\0 contains the entire match).

For example, for each change to a .c file in src/, we may want to compile the file and run its corresponding unit test:

sos src/ -c "gcc -c \0 -o obj/\1.o" -c "make test --filter=test/\1_test.c" -p "src/(.*)\.c"

Commands are run left-to-right, and one failed command will halt the entire pipeline.

The RCFile

As a shortcut, we may want to write the above only once and save it in .sosrc, which is an alternative to the command-line interface (yaml syntax):

- pattern: src/(.*)\.c
  commands:
  - gcc -c \0 -o obj/\1.o
  - make test --filter=test/\1_test.c

Then, we only need to run:

sos

to start watching the current directory. If you'd like to use multiple rcfiles, or just don't like the name .sosrc you can specify the rcfile on the command line like so:

sos --rcfile my-rcfile

Grammar

sosrc            := [entry]
entry            := { "pattern" | "patterns" : value | [value]
                    , "command" | "commands" : value | [value]
                    }
value            := [segment]
segment          := text_segment | var_segment
text_segment     := string
var_segment      := '\' integer

The .sosrc grammar is somewhat flexible with respect to the command specifications. Both singular and plural keys are allowed, and both strings and lists of strings are allowed for values.

Pipelining Explaned

Pipelines of commands are immediately canceled and re-run if a subsequent filesystem event triggers the same list of commands. Otherwise, commands are are enqueued and run sequentially to keep the terminal output clean and readable.

For example, we may wish to run hlint on any modified .hs file:

- pattern: .*\.hs
  command: hlint \0

We can modify foo.hs and trigger hlint foo.hs to run. During its execution, modifying bar.hs will enqueue hlint bar.hs, while modifying foo.hs again will re-run hlint foo.hs.