vaspian-test
Scratch / smoke-test topic — never wire production alerts here
Scratch topic for smoke-testing publishers and new phone subscriptions. **Never** wire production alerts here — anything on vaspian-test is assumed disposable.
ntfy.sh/vaspian-test · added 2026-05-13
Publishers
Every code path / config block that produces messages on this topic today. If you wire a new publisher, add it here.
Setting VMON_ALERT_TEST=1 in the environment swaps two values: (1) Brevo recipients narrow to caloi@vaspian.com only, (2) ntfy topic flips from vaspian-alerts → vaspian-test. The subject/title is also prefixed with '[TEST] ' so the alert is visually distinct on the phone. Used to dry-run a new VoIPMonitor alert rule against the real production DB without paging the ops list.
Ad-hoc verification: confirming a new phone subscription works, checking how a specific tag renders, or comparing how priority 5 behaves vs priority 1 on a given device. Publish to vaspian-test from any HTTP client per the ntfy docs.
How priorities are assigned
Whatever the sender feels like. Don't read anything into a P1 here — it's still a test.
Notes
- If you're subscribed to vaspian-test on your phone and you stop seeing notifications, double-check the topic name in the app — typos silently subscribe you to someone else's topic on the public broker.
vaspian-test on server ntfy.sh.