mirror of
https://github.com/agessaman/meshcore-bot.git
synced 2026-09-02 09:03:58 +00:00
agessaman
133a3bb595
Two documentation gaps behind open questions. The [External_Data] repeater_prefix_api_url comment claimed that leaving it empty "disables prefix command functionality" (#70). That is not what happens: the prefix command answers from the bot's own database of heard repeaters, and the API only augments it with node counts from a wider dataset. The wrong comment is a plausible reason the question was asked at all. Corrected, and the JSON contract is now documented in the command reference for anyone serving their own endpoint, since map.w0z.is is defunct and has no drop-in replacement. Also documented the pipx path (#222). The installer already grew a virtualenv in July, which covered the PEP 668 half of that report, but the unanswered part was where config.ini, the database and local/ live under a pipx install. They are all resolved relative to the directory containing config.ini, which means a bare `meshcore-bot` picks up whatever is in the current directory — so the guidance is to pass an absolute --config. Both console scripts are already smoke-tested from an installed wheel in CI, so this path is supported rather than incidental.