You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Document the HEALTH_CHECK_SMTP_PORT environment variable #42
The health check's email notifier accepts an optional SMTP port override, read
from the environment as HEALTH_CHECK_SMTP_PORT. When it is unset, the notifier
leaves the port to the mail transport's own default.
The README's environment variable table documents the host, user and password
for that notifier, but not the port. An operator whose SMTP relay listens
anywhere other than the default port therefore has no way to discover that the
knob exists short of reading the source.
Add a row for it to that table, alongside the other health check SMTP entries,
following the table's existing columns and wording conventions. It is optional,
and it has no default of its own.
Acceptance
The README's environment variable table contains a row for HEALTH_CHECK_SMTP_PORT.
The row describes it as the SMTP port for unhealthy notification emails and marks it optional, with column values consistent with the neighbouring host, user and password rows.
No other environment variable row is added, removed or reworded.
Note: this was a "make-work" issue created to test a piece of automation. It did represent a real gap in this code and in the downstream fork's branch. I didn't merge the result back upstream here because there's a bunch of other in-flight work in the fork as well, TBD soon. But for now, a successful test of a tiny piece of "night shift" automation.
Activity
ottonomy commentedon Sep 14, 2026
Night shift delivered.
nightshift/42-document-the-health-check-smtp-port-environment→maininskybridgeskills/dcc-signing-serviced2644118-6cd6-4438-8453-5983f3afeec9The pull request carries
agent-authored. Review it; do not trust itblindly. Departures and decisions the ticket did not specify are in its body.
ottonomy commentedon Sep 14, 2026
Note: this was a "make-work" issue created to test a piece of automation. It did represent a real gap in this code and in the downstream fork's branch. I didn't merge the result back upstream here because there's a bunch of other in-flight work in the fork as well, TBD soon. But for now, a successful test of a tiny piece of "night shift" automation.