Brandyn / Techy
d3ff452546
Deploying before the webhook exists is deliberate, so it must not depend on Alertmanager tolerating an empty webhook_url_file — which I could not verify. configure.py now generates the config and omits the Discord notifier entirely when ALERT_WEBHOOK_URL is unset: the receiver exists, drops notifications, and alerts still evaluate, group and show at /alerts. Setting the variable and re-applying turns delivery on. The URL stays in /etc/vanguard/alert-webhook rather than the config, because that file can be 0640 root:65534 for the container's user while the repo copy cannot. alertmanager.example.yml is the reference copy and is gitignored in generated form, like the other configs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
15 lines
318 B
Plaintext
15 lines
318 B
Plaintext
# never commit real secrets; copy the templates and edit the copies on the server
|
|
*.local.*
|
|
__pycache__/
|
|
.env
|
|
bot/app/__pycache__/
|
|
*.pyc
|
|
# generated by configure.py on the server — never commit or scp these
|
|
mediamtx.yml
|
|
copyparty.conf
|
|
observability/alertmanager.yml
|
|
Caddyfile
|
|
stream-token.secret
|
|
deploy.env
|
|
bot/app/
|