harbor-check-cli: SSH tunnel quick start
This CLI accesses a Harbor Check service running on a remote server through an SSH tunnel. It is useful when Harbor Check listens only on 127.0.0.1:8000.
Install
python -m pip install --upgrade harbor-check-cli
You need an SSH account on the remote server, and Harbor Check must be running there on 127.0.0.1:8000.
Open an SSH tunnel
Run this locally and keep the terminal open:
ssh -N -L 8000:127.0.0.1:8000 YOUR_SERVER_USERNAME@YOUR_SERVER_HOST
If local port 8000 is busy, choose another local port and use it consistently below.
Log in through the tunnel
In a second terminal:
harbor-check login \
--server http://127.0.0.1:8000 \
--username YOUR_SERVER_USERNAME
Enter the password when prompted. The token is stored in ~/.config/harbor-check/credentials.json with permissions restricted to the current user.
Use the CLI
harbor-check tasks
# List currently running tasks globally
harbor-check running
# Limit the list to one username
harbor-check running --username USERNAME
# Limit it to one username and folder
harbor-check running --username USERNAME --folder FOLDER_NAME
harbor-check folders
harbor-check folder-tasks FOLDER_NAME
harbor-check task USER/FOLDER/TASK_NAME --detail
harbor-check stop USER/FOLDER/TASK_NAME
harbor-check restart USER/FOLDER/TASK_NAME
Upload a task directory through the same tunnel:
harbor-check upload ./my-task \
--username YOUR_SERVER_USERNAME \
--server http://127.0.0.1:8000
Put --json before the subcommand for machine-readable output:
harbor-check --json tasks
harbor-check --json running --username USERNAME
Troubleshooting
Connection refused: the SSH tunnel is closed, the local port is wrong, or Harbor Check is not listening on127.0.0.1:8000on the server.- An HTML error page: use the tunnel address
http://127.0.0.1:8000, not the server's public address. - Login failure: verify the server username and password accepted by the Harbor Check deployment.
Metadata
Release files for harbor-check-cli 0.1.18
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 |
|---|---|---|---|---|
| harbor_check_cli-0.1.18.tar.gz | 7.0 kB | Without provenance | Details for harbor_check_cli-0.1.18.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| harbor_check_cli-0.1.18-py3-none-any.whl | Python 3 | none | any | Details for harbor_check_cli-0.1.18-py3-none-any.whl |
Total release size: 15.0 kB
Release files / harbor_check_cli-0.1.18.tar.gz
| Download URL | harbor_check_cli-0.1.18.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
97931069e9dca2960ff2c5c0dbb87e4305da797ddf92def708a2de6d437e1e1a
|
|
BLAKE2b-256 checksum How to use checksums |
9e497260f592da8851341ef3eb57fcbaffe436ecdbe0180eefc0f4dc43f29f03
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / harbor_check_cli-0.1.18-py3-none-any.whl
| Download URL | harbor_check_cli-0.1.18-py3-none-any.whl |
|---|---|
| Size | 8.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e16dc3fd5b876dcc89d21002cfe04d535f5bb685cf83f2ac8ceb1a69fef7bdd4
|
|
BLAKE2b-256 checksum How to use checksums |
41f8d90f00967859f9b0b181a463b2523f8f69dfe639f88c2ae99ad3c2577d3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for harbor-check-cli 0.1.18
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.