plesty-server · plesty-bench
The bench PC's own console for the PLESTY platform. It installs hub device
modules, starts and supervises their device servers, runs field tests against
the real instruments and keeps the logs — so a lab bench is set up and kept
running from one place instead of one venv, one terminal and one hand-written
uv pin per instrument.
This repository publishes two packages:
| Install on | Install with | |
|---|---|---|
plesty-server — the bench application: CLI, Qt console, agent |
the bench PC | uv tool install "plesty-server[gui]" |
plesty-bench — the client that drives a bench from elsewhere |
your own machine | uv tool install plesty-bench |
On a Windows bench, the releases
carry a setup.exe (per-user, no admin); macOS and Linux have install.sh.
Both install uv, run the command above and add a Start-menu / Launchpad
entry — they contain no application code of their own.
Bringing up a bench
plesty-server fleet init # a fleet.yaml to declare into
plesty-server declare pm100d plesty-pm100d --version 0.2.1 \
--arg --address --arg "USB0::0x1313::…::INSTR"
plesty-server start pm100d # installs, launches, waits until it answers
plesty-server status
The instrument is now reachable from an experiment PC at this machine's
address on the port status reports. plesty-server gui opens the same bench
in a window; plesty-server fleet run keeps it up headless after a reboot.
Driving it from your own machine
The bench serves an agent; the client sends it plesty-server command lines
and follows the output.
plesty-bench -b lab-bench-03 status
plesty-bench -b lab-bench-03 field-test pm100d --gates connect,drain
plesty-bench -b lab-bench-03 control pm100d # a control panel per device
Documentation
Full documentation — start there if anything below is unfamiliar. It is in two parts.
Using a bench, in the order you meet it:
| Setting up a bench | The fleet file, declaring devices, ports, the .env |
| Device modules | The catalogue, installing, several versions side by side |
| Running device servers | Start, stop, status, logs, the working fleet, headless benches |
| Field tests | Running a module's field test against the instrument |
| The console | Every part of the window, and the control panels |
| Working remotely | The agent and the plesty-bench client |
| Maintenance | Upgrading, clearing logs, purging, uninstalling |
| Command reference | Every plesty-server command |
Design and internals is the other part: the architecture, the process model, the port rules, the installer, the agent protocol, the platform differences and the release machinery — for contributors, and for anyone debugging behaviour that only makes sense once the mechanism is visible.
New to the platform? The PLESTY quickstart runs a whole experiment against a bench and is the gentlest way in.
1 maintainer
Metadata
1 maintainer
Release files for plesty-bench 0.3.4
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 |
|---|---|---|---|---|
| plesty_bench-0.3.4.tar.gz | 545.4 kB | Without provenance | Details for plesty_bench-0.3.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| plesty_bench-0.3.4-py3-none-any.whl | Python 3 | none | any | Details for plesty_bench-0.3.4-py3-none-any.whl |
Total release size: 562.3 kB
Release files / plesty_bench-0.3.4.tar.gz
| Download URL | plesty_bench-0.3.4.tar.gz |
|---|---|
| Size | 545.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ee0783d4c358030bd5098bbbf67b6bca01e0f73c02476ec0704cdbd366dcd5c
|
|
BLAKE2b-256 checksum How to use checksums |
6691e3694da67407148fc84e2718f6e9fffc8411443762ff98739503a7bebd70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.9.30 {"installer":{"name":"uv","version":"0.9.30","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"12","id":"bookworm","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / plesty_bench-0.3.4-py3-none-any.whl
| Download URL | plesty_bench-0.3.4-py3-none-any.whl |
|---|---|
| Size | 16.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63e4f8163f86e1fc1f45cf6b89aef3cf0379b5f78131c28f19f459d6b2eb2bee
|
|
BLAKE2b-256 checksum How to use checksums |
097b0154fae8d7f59fbf5b3d24e8b2105c41cbf108e4f3865dc887d736e975be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.9.30 {"installer":{"name":"uv","version":"0.9.30","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"12","id":"bookworm","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for plesty-bench 0.3.4
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.
