docs(ntfy): ntfy publishes a host port for the external reverse proxy #37

wtclaude · 2026-07-22T08:58:29Z

wtclaude commented

2026-07-22 08:58:29 +00:00

Documentation companion to RunicGateway/website#95.

The ntfy relay is reached through the public reverse proxy, which runs outside the compose network and can only reach a service via a published host port (the same reason app publishes 3000). The docs previously described ntfy as having "no published host port / internal-only publisher," which never matched a working deployment.

Changes

android/PLAN.md — §11 (deployment) and §13 (open items): ntfy publishes :80 on a host port (NTFY_HOST_PORT, default 2586); the reverse proxy forwards the notification subdomain to it. Both devices (SSE subscribe) and the backend publisher (POSTing tickles to registered device endpoints) reach ntfy on that public origin — no separate internal publish path.
website/BACKEND_DESIGN.md — compose-topology section + the .env.example block: document the published port and NTFY_HOST_PORT.

AI-assisted: authored with Claude (Claude Code).

🤖 Generated with Claude Code

Documentation companion to **`RunicGateway/website#95`**. The ntfy relay is reached through the public reverse proxy, which runs **outside** the compose network and can only reach a service via a **published host port** (the same reason `app` publishes `3000`). The docs previously described ntfy as having "no published host port / internal-only publisher," which never matched a working deployment. ## Changes - **`android/PLAN.md`** — §11 (deployment) and §13 (open items): ntfy publishes `:80` on a host port (`NTFY_HOST_PORT`, default `2586`); the reverse proxy forwards the notification subdomain to it. Both devices (SSE subscribe) and the backend publisher (POSTing tickles to registered device endpoints) reach ntfy on that public origin — no separate internal publish path. - **`website/BACKEND_DESIGN.md`** — compose-topology section + the `.env.example` block: document the published port and `NTFY_HOST_PORT`. --- - [x] AI-assisted: authored with Claude (Claude Code). 🤖 Generated with [Claude Code](https://claude.com/claude-code)

wtclaude added 1 commit 2026-07-22 08:58:30 +00:00

docs(ntfy): ntfy publishes a host port for the external reverse proxy 0d5c0486dd

Match the website change: the ntfy relay is reached through the public
reverse proxy, which runs outside the compose network and can only reach
a service via a published host port. Update the "no published host port /
internal-only publisher" claims in android/PLAN.md (§11 + §13) and
website/BACKEND_DESIGN.md to describe the published NTFY_HOST_PORT
(default 2586 -> ntfy:80), and note that both devices and the backend
publisher reach ntfy on the public origin.

Co-Authored-By: Claude <noreply@anthropic.com>

whitlocktech approved these changes 2026-07-22 08:59:13 +00:00

whitlocktech merged commit 7d7df6ac15 into main

2026-07-22 08:59:20 +00:00

whitlocktech deleted branch fix/ntfy-published-port

2026-07-22 08:59:21 +00:00

whitlocktech referenced this issue from a commit

2026-07-22 08:59:22 +00:00

Merge pull request 'docs(ntfy): ntfy publishes a host port for the external reverse proxy' (#37) from fix/ntfy-published-port into main

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/docs#37