Skip to content

Document the HEALTH_CHECK_SMTP_PORT environment variable #42

Closed
skybridgeskills/dcc-signing-service
#8

Description

@ottonomy

What to build

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.

Effort: workspace/2026-09-13-dcc-agent-tooling

Activity

  1. added
    agent-readyJudged workable by an unattended agent right now
    on Sep 14, 2026
  2. self-assigned this
    on Sep 14, 2026
  3. ottonomy commented on Sep 14, 2026

    @ottonomy
    Author

    Night shift delivered.

    pull request skybridgeskills#8
    branch nightshift/42-document-the-health-check-smtp-port-environment → main in skybridgeskills/dcc-signing-service
    commits 1
    turns / cost 16 / $0.54
    Agent-Run d2644118-6cd6-4438-8453-5983f3afeec9

    The pull request carries agent-authored. Review it; do not trust it
    blindly. Departures and decisions the ticket did not specify are in its body.

  4. ottonomy commented on Sep 14, 2026

    @ottonomy
    Author

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

agent-readyJudged workable by an unattended agent right now

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions