The Discord bot can speak instead of only answering, Podman remote hosts can have their own SSH keys, and there is a new logo.
The Discord bot got a voice
Every slash-command reply is ephemeral — visible only on the device that sent it, and it deletes itself. That is right for an answer naming your internal services, and useless for "bot started" or a crash alert. The bot could respond; it could not speak.
Give it a channel ID and it posts there of its own accord — permanent, visible to everyone in that channel. It is a notification channel like any other, with its own card, switch and Send test button.
Command answers can be made public too, which was @NotRetarded's argument rather than mine and the better one: an ephemeral answer also tidies itself away, and whether you want that depends on whose channel it is. Off by default.
Both were built against his testing and confirmed by him on a real server — including the part I could not check from here, that a slow command like /updateall behaves the same as a fast one. It does, because the visibility flag has to be set on the acknowledgement: Discord fixes it there and the later edit cannot change it.
With both the webhook and the bot channel configured, every notification arrives twice. He asked for a rule forbidding that; the page says it instead — you might want one public and one private.
Podman: per-host SSH keys
A host in DOCKER_HOSTS may now be context://<name>, which runs podman --connection <name> or docker --context <name>.
The reason is worse than convenience. Measured:
podman --url ssh://user@host …
takes the identity of the default connection — whatever host that points at, not the one whose URI matches — and it ignores ~/.ssh/config completely, where docker -H ssh:// reads it because it shells out to the real ssh. So on Podman there was no way to give each host its own key, and anyone whose keys live in ~/.ssh/config got a failure that looked like an unreachable machine.
Which brings us to:
An unreachable host now says why
The Status page printed nas: unreachable for a wrong key, a closed port, a DNS failure and a wrong socket path alike — while Telegram and Discord had always quoted the CLI. The CLI's own last line is shown now, where those four are plainly distinguishable.
Deliberately unclassified, incidentally: Podman's first error line sends you to podman machine init, which is never the answer for a remote host.
A new logo
The mark is a tile; the wordmark next to it is real HTML — so it stays sharp at any pixel density and follows your light/dark theme instead of being baked into an image. The favicon is the same tile, which the old one (a shield with an eye) was not. logo.png drops from 1.4 MB to 92 KB.
And
- "Docksentry started" only ever went to Telegram. Not to Discord, e-mail or ntfy — not since notifier channels existed. The hard-kill note and the what's-new note sitting beside it in the code have always gone to every channel; that line never had a second recipient.
- Everything Discord is one card on the Connections page. Webhook, bot and bot channel were three, in a list sorted by state, which put them anywhere.
VERIFICATION.mdsaid "How Docksentry v? is checked" for any pre-release.
Nothing to do on upgrade. docs/podman.md is new if you run Podman; context:// is optional and ssh:// keeps working where it already did.
