mirror of
https://github.com/kuhyx/signal-bot.git
synced 2026-11-10 19:27:20 +01:00
Krzysztof kuhy Rudnicki
72e90acb47
A custom alias is data the command table is built from, so it cannot be a live switch like the ones already on the tab. Instead the management page writes aliases_custom.json in the bot's state directory and then asks the bot to reload, in one step: whenever the answer is anything but `reloaded` -- a word another command has, a name no command has, a bot still connecting -- the file is restored byte for byte and the bot's own reason is shown next to the field. What is on disk is therefore always what the bot serves, and a typo cannot sit in the file poisoning every later reload. The registry appends the operator's words to the shipped list at registration, which keeps `!pomoc` on the shipped spelling and routes the new words through the same clash check as aliases.json. An alias for a name no command has fails the whole build (ConfigError -> `kept`), because a silently ignored entry is how a file drifts. The tagger treats custom aliases as reserved words too, so a person cannot be given one. registry.py crossed the 250-line cap and now re-exports the record and the error types from command.py; the bot's state directory lookup, previously duplicated in pack.py and the suggestions export, is state_dir.py. Proven end to end: !e2ekot is unknown, the file is written and reload.sh runs, !e2ekot posts a cat, a file naming a command that does not exist is refused with 409 and the previous table still answers. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
31 lines
1.2 KiB
Python
31 lines
1.2 KiB
Python
# Copyright (c) 2026 Krzysztof Rudnicki. MIT licence.
|
|
"""Where the bot keeps what is not in this repository.
|
|
|
|
One answer for every file that has to live outside the tree -- the album,
|
|
the suggestions export, the operator's own aliases -- so that the bot and
|
|
the management page, two processes reading the same environment, cannot
|
|
disagree about where a file is.
|
|
"""
|
|
|
|
from __future__ import annotations
|
|
|
|
import os
|
|
from pathlib import Path
|
|
|
|
|
|
def state_dir() -> Path:
|
|
"""The directory for data this repository never sees.
|
|
|
|
Read straight off os.environ rather than from a passed mapping, exactly
|
|
as portraits.default_cache_dir is: .env has already been loaded into the
|
|
environment by then, and it is what lets one autouse fixture keep the
|
|
whole test suite away from the operator's real data. STATE_DIRECTORY
|
|
comes before anything under $HOME because that is the directory systemd
|
|
creates and exposes regardless of ProtectHome.
|
|
"""
|
|
state = os.environ.get("STATE_DIRECTORY", "").strip()
|
|
if state:
|
|
return Path(state)
|
|
home = os.environ.get("XDG_DATA_HOME", "").strip() or str(Path.home() / ".local" / "share")
|
|
return Path(home) / "signal-bot"
|