Files
axion1337.chat-gitops/host-config/maintenance-notify/config.example
T
Thore CimbalandClaude Sonnet 5 376772078a feat: pre-update maintenance notifications via mail + matrix (Issue #24)
unattended-upgrades was already active on the host, just never documented
or closed. Adds a generic, reusable systemd timer + script that fires
before the daily update window and notifies via email and a Matrix thread
reply if any packages are actually pending - reusing the mas-cli bot
account pattern established for Draupnir.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-29 12:00:00 +00:00

29 lines
1.4 KiB
Plaintext

# Example for /etc/maintenance-notify/config (host-level, NOT deployed via
# GitOps/Flux - copy manually to the target host and adjust for your own
# instance). Sourced as a plain bash file by maintenance-notify.sh.
#
# The values below are axion1337.chat's own, real configuration - shown as a
# concrete worked example. Replace every value for your own homeserver/room.
# Your homeserver's base URL (matrix client-server API). This is often a
# dedicated subdomain, NOT your apex domain - check your own
# .well-known/matrix/client delegation (`m.homeserver.base_url`) to be sure.
# For axion1337.chat specifically it's matrix.axion1337.chat, not the apex.
MATRIX_HOMESERVER="https://matrix.axion1337.chat"
# The room the notification gets posted into.
MATRIX_ROOM_ID="!lmZaajvVboTPxQxXzv:axion1337.chat"
# The thread to reply into (matrix.to link's event id after the room id).
# IMPORTANT: Matrix event IDs start with "$" - this value MUST be
# single-quoted, otherwise bash will try to expand "$T3MQZgf..." as a
# variable and silently truncate it to an empty string.
MATRIX_THREAD_EVENT_ID='$T3MQZgf-maQwfshCKlCn0bo4DGHn4sZS-8eI9u2V6ZI'
# Sending identity - must match the "user"/"from" in /etc/msmtprc.
MAIL_FROM="wartung@axion1337.chat"
# Where the pre-update heads-up actually lands (your everyday inbox, not
# necessarily the sending mailbox above).
MAIL_TO="your-address@example.com"