The objective of BuffaloFQ is to provide a very simple and reliable method of moving files around an architecture.
Background, Examples, and FAQ
Please see the Wiki: https://github.com/kenfar/buffalofq/wiki
Installation:
$ pip install buffalofq
Configuration:
Most configuration is handled through a simple yaml file, that is kept in the xdg-compliant config directory. On linux this would be:
$HOME/.config/buffalofq_mover/[config-name1].yml
$HOME/.config/buffalofq_mover/[config-name2].yml
$HOME/.config/buffalofq_mover/[config-name3].yml
Config example:
name: ids_to_load #
status: enabled # choices are: enabled, disabled
polling_seconds: None # delay in seconds between checks for new files, defaults to 300
limit_total: -1 # choices: -1 (run continuously), 0 (run until source_dir is empty), [some number] run until this number have been moved.
port: None # defaults to 22
key_filename: None # defaults to id_buffalofq_rsa
log_dir: /data/logs # location buffalofq_mover will write its logs
log_level: None # choices are: info, warning, error, critical, defaults to debug
sort_key: time # choices are: None, name, or name of a field within filename, defaults to None
source_host: localhost # must be localhost at this time
source_user: None # not yet used, defaults to current userid
source_dir: /data/output #
source_fn: ‘*’ # wild-card for selecting source files
source_post_dir: /data/archive #
source_post_action: move # choices: move, delete, None
dest_host: datawarehouse #
dest_user: None # used to log into dest_host, defaults to current userid
dest_dir: /data/input #
dest_fn: None # needed if dest_post_action is symlink or move
dest_post_dir: None # not used yet
dest_post_action: None # choices: symlink, move, None
Run:
To run once, you can simply run it like:
$ ./buffalofq_mover –config-name [config-name1]
A trivial way to keep it running continuously:
$ nohup ./buffalofq_mover –config-name [config-name1] &
0.0.3 - add dest_post_action of move - change config values of pass to None - add config defaults & validation - housekeeping
0.0.2 - initial genuinely usable working version - add ability to receive files in order of their name, or any field within the name - add ability to provide name of ssh key to use - rename audit file & buffalofq program to buffalofq_mover - misc general improvements and refactorings
0.0.1 - initial working version
Metadata
Release files for buffalofq 0.0.3
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 |
|---|---|---|---|---|
| buffalofq-0.0.3.tar.gz | 11.5 kB | Without provenance | Details for buffalofq-0.0.3.tar.gz |
Release files / buffalofq-0.0.3.tar.gz
| Download URL | buffalofq-0.0.3.tar.gz |
|---|---|
| Size | 11.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4ff609c579b07c286396137361fed90a80bcd109df9e0f051ab688ddc62e9cf2
|
|
BLAKE2b-256 checksum How to use checksums |
30df54ac3062468c11e85a9f70fa3edf734ca2f31a9ffa269254da259dc9c94d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for buffalofq 0.0.3
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.