Add shell wrapper for Gitea config menu #34

New Issue

2026-07-02T00:47:52-05:00

jcwalker3 commented

2026-07-02 00:47:52 -05:00

Context

Running the interactive config menu with the system Python can fail when dependencies such as python-dotenv are installed only in the project virtual environment:

python3 gitea_config.py menu
ModuleNotFoundError: No module named 'dotenv'

The menu itself exists (python gitea_config.py menu), but operators need a simple shell entrypoint that consistently uses the repo virtual environment when available.

Scope

Add a small shell wrapper for launching the Gitea config menu.

Suggested behavior:

Prefer ./venv/bin/python when present.
Fall back to python3 only when the venv is unavailable.
Run gitea_config.py menu with all passed arguments.
Fail with a clear message if required Python dependencies are missing.
Do not print, read, or expose tokens/secrets.

Acceptance criteria

A shell wrapper can launch the existing interactive menu without requiring users to remember the venv interpreter path.
The wrapper does not implement menu logic itself.
The wrapper does not create or modify profile config unless the existing menu does so through normal user interaction.
No secrets, tokens, auth headers, or credential file contents are printed.
README or runbook usage is updated if needed.
Tests or a lightweight smoke check validate the wrapper reaches the menu/help path without dependency import failures.

Non-goals

Do not change MCP runtime behavior.
Do not add new Gitea API operations.
Do not change credential storage semantics.
Do not bypass the canonical profile config model.

## Context Running the interactive config menu with the system Python can fail when dependencies such as `python-dotenv` are installed only in the project virtual environment: ```text python3 gitea_config.py menu ModuleNotFoundError: No module named 'dotenv' ``` The menu itself exists (`python gitea_config.py menu`), but operators need a simple shell entrypoint that consistently uses the repo virtual environment when available. ## Scope Add a small shell wrapper for launching the Gitea config menu. Suggested behavior: * Prefer `./venv/bin/python` when present. * Fall back to `python3` only when the venv is unavailable. * Run `gitea_config.py menu` with all passed arguments. * Fail with a clear message if required Python dependencies are missing. * Do not print, read, or expose tokens/secrets. ## Acceptance criteria * A shell wrapper can launch the existing interactive menu without requiring users to remember the venv interpreter path. * The wrapper does not implement menu logic itself. * The wrapper does not create or modify profile config unless the existing menu does so through normal user interaction. * No secrets, tokens, auth headers, or credential file contents are printed. * README or runbook usage is updated if needed. * Tests or a lightweight smoke check validate the wrapper reaches the menu/help path without dependency import failures. ## Non-goals * Do not change MCP runtime behavior. * Do not add new Gitea API operations. * Do not change credential storage semantics. * Do not bypass the canonical profile config model.

jcwalker3 added the status:in-progress label 2026-07-02 00:50:24 -05:00

jcwalker3 commented

2026-07-02 00:50:38 -05:00

Starting implementation for the shell wrapper. Scope: add a small launcher for the existing Gitea config menu, update usage docs, run wrapper smoke checks and tests. No MCP runtime behavior or credential semantics changes intended.

jcwalker3 referenced this issue from a commit

2026-07-02 01:01:18 -05:00

fix: add Gitea config menu wrapper (#34)

jcwalker3 referenced a pull request that will close this issue

2026-07-02 01:05:11 -05:00

fix: add Gitea config menu shell wrapper (#34) #35

jcwalker3 closed this issue

2026-07-02 01:09:03 -05:00

jcwalker3 referenced this issue

2026-07-02 01:26:25 -05:00

Improve Gitea config menu UX #36

sysadmin removed the status:in-progress label 2026-07-02 01:30:25 -05:00