Helix P4P caching extensions
Project description
Helix Perforce Proxy - Cache
helix-p4p is a proxy cache for Perforce servers.
Flush
As revisions are added to files within the proxy, there is no internal cache expiry performed. Thus, a proxy server can retain excessive amounts of cached file revisions.
p4p-flush allows sysadmins to periodically expire content.
usage: p4p-flush [-h] [--ttl TTL] [--min-vers MIN_VERS] [--purge] path
Flush helix-p4p cache
positional arguments:
path
options:
-h, --help show this help message and exit
--ttl TTL Expiry time (hours)
--min-vers MIN_VERS Number of revisions to keep
--purge Remove expired items from disk
Systemd
helix-p4p-sync
Oneshot for syncing a proxy
# 'example' is a given configuration name
systemctl enable helix-p4p-sync@example
systemctl start helix-p4p-sync@example
helix-p4p
Service for running a Helix P4P server.
# 'example' is a given configuration name
# Create a user to run the proxy and set the proxy root directory
useradd -m -d /opt/perforce/example -s /bin/sh example
su example -c "mkdir -p /opt/perforce/example/{root,cache}"
systemctl enable helix-p4p@example
systemctl start helix-p4p@example
TODO
- Humanize file size outputs, such that automatic care is taken betwen bytes/MB/GB.
- Read in argparse config variables from the environment.
- Expand on test cases, expressing more edge cases.
- Add Systemd scripts for configuration & running.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
helix-p4p-cache-0.0.1.tar.gz
(4.9 kB
view hashes)
Built Distribution
Close
Hashes for helix_p4p_cache-0.0.1-py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | 5cd5f3f015779c6bb5d3a79018f36bc714ba0b6c1287843b981e5d105b9c51d1 |
|
MD5 | a5322b8149af4b66e5b0b17dae96746f |
|
BLAKE2b-256 | 59bd20b4ef12575e269fa94d37a19428f95c9b9ad1d6f29f4acd301badcca2ed |