Using launchd to watch a filesystem directory and upon create/change to a file with the directory, execute a command.
For this example:
- Watching directory of:
/path/to/watch. - Upon file change, execute:
/path/to/command argument1 argument2.
Using launchd to watch a filesystem directory and upon create/change to a file with the directory, execute a command.
For this example:
/path/to/watch./path/to/command argument1 argument2.| root = true | |
| [*] | |
| charset = utf-8 | |
| end_of_line = lf | |
| indent_size = 2 | |
| indent_style = tab | |
| insert_final_newline = true | |
| trim_trailing_whitespace = true |
| { | |
| "root": true, | |
| "parserOptions": { | |
| "sourceType": "module" | |
| }, | |
| "env": { | |
| "es2020": true, | |
| "node": true | |
| }, | |
| "extends": [ |
A function hash_json(data), accepting a structure loaded from json.load() and computing a hash.
$ ./hashjson.py
Hash a.json: 8212462b8e9ce805cac2f0758127c5cfd7710baf
Hash b.json: 8212462b8e9ce805cac2f0758127c5cfd7710bafTip
By default npm publish will publish all files within a working directory - excluding .gitignore / .npmignore / package-lock.json.
This is typically fine, but often I find myself leaving un-staged files (e.g. TODO.txt files) in a repository root and these of course get accidently taken along for the publish ride.
Helper script npm-publish-wrap.sh will catch calls to npm publish and:
.git directory) found.From what I can see, there is no simple way to extract a list of installed Datadog integrations for documentation/etc. purposes.
Here is a lo-fi method of pulling it from the web UI DOM: