fix: listener daemon read config from wrong HOME
enable_service baked Environment=HOME=$HOME into the unit at enable time; a stale/wrong shell HOME made the daemon read an empty ~/.config/linux_post_install/telegram_commands.env — commands showed in the bot menu (synced from the editor's correct HOME) but replying said "unknown command" and /help said none mapped. systemd user services already set the correct HOME; stop pinning it.
This commit is contained in:
@@ -556,7 +556,7 @@ Use conventional prefixes: `feat:`, `fix:`, `docs:`, `refactor:`, `chore:`
|
||||
| `features/autostart.sh` | 14 | Boot-time feature (moved from `bin/`, flag-gated service) |
|
||||
<!-- GEN:START filetable -->
|
||||
| `bin/pos` | 272 | CLI dispatcher with smart arg matching + logging + category help |
|
||||
| `bin/pos-communication-telegram-listener` | 509 | Telegram bot listener: map /command → bash, run them on chat messages |
|
||||
| `bin/pos-communication-telegram-listener` | 511 | Telegram bot listener: map /command → bash, run them on chat messages |
|
||||
| `bin/pos-communication-telegram-sender` | 220 | Send Telegram messages/files/links/stickers via Bot API (send, test) |
|
||||
| `bin/pos-config` | 80 | Interactive editor for the tools' runtime config (reads # POS_CONFIG: registry) |
|
||||
| `bin/pos-docker-compose` | 366 | Docker Compose service manager (ls/up/down/restart/logs/update/config) |
|
||||
|
||||
Reference in New Issue
Block a user