Document installing cv4pve-tui as a uv tool #28

Merged

Duckboot merged 1 commits from docs/install-as-tool-17 into main

2026-11-03 01:32:52 +01:00

Author	SHA1	Message	Date
DuckbootandClaude Opus 5.5	ff6345c80f	Document installing cv4pve-tui as a uv tool CI / pytest and ruff (pull_request) Successful in 4m40s Details CI / pytest and ruff (push) Has been cancelled Details The README gets an "Install" section: install with uv tool from the Gitea repo or from a local checkout, then upgrade and uninstall. The "Run" section says to use `cv4pve-tui` when installed and `uv run cv4pve-tui` from a checkout. Verified by installing into throwaway tool dirs (UV_TOOL_DIR and UV_TOOL_BIN_DIR under /tmp): `uv tool install .` gave a cv4pve-tui binary. Started from /tmp in a pseudo-terminal, it drew the guest frame and ran until it was stopped. The pyproject metadata (entry point, readme, requires-python) was already enough. Closes #17 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-03 00:31:01 +01:00

Author

SHA1

Message

Date

DuckbootandClaude Opus 5.5

ff6345c80f

Document installing cv4pve-tui as a uv tool

CI / pytest and ruff (pull_request) Successful in 4m40s

Details

CI / pytest and ruff (push) Has been cancelled

Details

The README gets an "Install" section: install with uv tool from the
Gitea repo or from a local checkout, then upgrade and uninstall. The
"Run" section says to use `cv4pve-tui` when installed and
`uv run cv4pve-tui` from a checkout.

Verified by installing into throwaway tool dirs (UV_TOOL_DIR and
UV_TOOL_BIN_DIR under /tmp): `uv tool install .` gave a cv4pve-tui
binary. Started from /tmp in a pseudo-terminal, it drew the guest
frame and ran until it was stopped. The pyproject metadata (entry
point, readme, requires-python) was already enough.

Closes #17

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-03 00:31:01 +01:00