cqh_file_watcher
something like File-Watcher for vscode
Usage
cqh_file_watcher -c ***.conf
conf example
use pattern
{"command_list":[
{
"pattern": "*.py",
"command": "sudo supervisorctl restart redis"
}
],
"directory": "/home/vagrant/code/code1"
}
no pattern
{"command_list":[
{
"command": "echo things changed"
}
],
"directory": "/home/vagrant/code/code1"
}
directory for command
{"command_list":[
{
"pattern": "*.py",
"command": "sudo supervisorctl restart redis"
"directory": "/home/vagrant"
}
]
"directory": "/home/vagrant/code/code1"
}
add ignore pattern for one
{"command_list":[
{
"pattern": "*.py",
"ignore_pattern": ["_build/.*"],
"command": "sudo supervisorctl restart redis"
"directory": "/home/vagrant"
}
]
"directory": "/home/vagrant/code/code1"
}
add ignore pattern for multi
{"command_list":[
{
"pattern": "*.py",
"ignore_pattern": ["_build/.*" , "_download/.*", "^css/.*", "^_static/.*"],
"command": "sudo supervisorctl restart redis"
"directory": "/home/vagrant"
}
]
"directory": "/home/vagrant/code/code1"
}
use DIRECTORY env
{"command_list":[
{
"pattern": "*.py",
"ignore_pattern": ["_build/.*" , "_download/.*", "^css/.*", "^_static/.*"],
"command": "sudo supervisorctl restart redis"
"directory": "/home/vagrant"
}
]
"directory": "${DIRECTORY}"
}
some problems
sre_constants.error: nothing to repeat at position 0
config
{"command_list":[
{
"pattern": "*\\.py",
"ignore_pattern": ["_build/.*" , "_download/.*", "^css/.*", "^_static/.*"],
"command": "${DIRECTORY}/venv/bin/invoke gpush"
}
],
"directory": "${DIRECTORY}"
}
replace pattern: "*\\.py" with patter: ".*\\.py"
Metadata
Release files for cqh-file-watcher 0.0.41
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cqh_file_watcher-0.0.41.tar.gz | 6.9 kB | Without provenance | Details for cqh_file_watcher-0.0.41.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cqh_file_watcher-0.0.41-py3-none-any.whl | Python 3 | none | any | Details for cqh_file_watcher-0.0.41-py3-none-any.whl |
Total release size: 15.3 kB
Release files / cqh_file_watcher-0.0.41.tar.gz
| Download URL | cqh_file_watcher-0.0.41.tar.gz |
|---|---|
| Size | 6.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e1c2fac5d464adbf647aaf1b41325af4b5fabfb2b46978e916bc384e4ac5f711
|
|
BLAKE2b-256 checksum How to use checksums |
4a48f5b8759a1925cfec7c7261a352cb2ceecd77fb443335914b07959bd9f95d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/33.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.11.2 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.8.10
|
Release files / cqh_file_watcher-0.0.41-py3-none-any.whl
| Download URL | cqh_file_watcher-0.0.41-py3-none-any.whl |
|---|---|
| Size | 8.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8a1627e94958c696717041c96a2c79baa068142bfee7e9f71eabe81313030fd4
|
|
BLAKE2b-256 checksum How to use checksums |
41cc472c92349f6e34e1c8bd7c3b3b3cb86a004ab6005207d47a68dbbc2094da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/33.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.11.2 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.8.10
|
Security for cqh-file-watcher 0.0.41
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.