No deployed planish service — README NodeHub deploy-on-push claim unimplemented (zero webhooks) #17

New issue

Closed

opened 2026-08-14 06:19:55 +00:00 by Mark · 1 comment

Mark commented

2026-08-14 06:19:55 +00:00

Owner

Source: Kanban QA card t_24babe4e (post-deploy probe for AuWoMe/planish#15)

Summary

The README states planish "Deploys to NodeHub via Forgejo webhook on push to main", but no webhook is configured and no planish app exists on Node Hub — the post-deploy health check has no live target.

Actual behavior

GET /api/v1/repos/AuWoMe/planish/hooks returns [] (zero webhooks configured).
Node Hub API (nodehub.tail018ac4.ts.net:8000) lists 11 apps — none is planish.
No listener on ports 3000/8080; no planish podman container or running next process. Only artifact is a 6-day-old local docker image localhost/planish:security-test.

Expected behavior

A webhook on this repo posts push events to Node Hub, which deploys planish; a planish app appears in Node Hub's app list and is reachable on the expected port.

Reproduction steps

GET /api/v1/repos/AuWoMe/planish/hooks — returns empty array.
Query Node Hub app list — no planish entry.
ss -ltn | grep -E '3000|8080' — no listener.

Impact

Merged fixes to main are never deployed; "post-deploy" verification cannot run against a live service.

Ref: kanban card t_24babe4e.

**Source:** Kanban QA card `t_24babe4e` (post-deploy probe for AuWoMe/planish#15) ## Summary The README states planish "Deploys to NodeHub via Forgejo webhook on push to main", but no webhook is configured and no planish app exists on Node Hub — the post-deploy health check has no live target. ## Actual behavior - `GET /api/v1/repos/AuWoMe/planish/hooks` returns `[]` (zero webhooks configured). - Node Hub API (nodehub.tail018ac4.ts.net:8000) lists 11 apps — none is planish. - No listener on ports 3000/8080; no planish podman container or running next process. Only artifact is a 6-day-old local docker image `localhost/planish:security-test`. ## Expected behavior A webhook on this repo posts push events to Node Hub, which deploys planish; a planish app appears in Node Hub's app list and is reachable on the expected port. ## Reproduction steps 1. `GET /api/v1/repos/AuWoMe/planish/hooks` — returns empty array. 2. Query Node Hub app list — no planish entry. 3. `ss -ltn | grep -E '3000|8080'` — no listener. ## Impact Merged fixes to `main` are never deployed; "post-deploy" verification cannot run against a live service. Ref: kanban card `t_24babe4e`.

Mark added the

chore

label

2026-08-14 06:19:55 +00:00

Mark added the

triage-approved

label

2026-09-15 15:36:49 +00:00

Mark referenced this issue from a commit

2026-09-18 23:20:58 +00:00

docs(readme): correct false NodeHub deploy-on-push claim (fixes #17)

Mark closed this issue

2026-09-18 23:20:58 +00:00

Mark commented

2026-09-18 23:21:27 +00:00

Author

Owner

Closed via commit b7216bd on origin/main (after rebase on bae00a1). The README Deployment section no longer claims a webhook-driven NodeHub deploy that does not exist; it now describes the actual state (no deploy workflow, no webhook, no NodeHub app) and points to manual-deploy and future-pipeline inputs. See Dockerfile and .forgejo/workflows/ci.yml for the build inputs any future deploy pipeline will need. -- triage-runner

Closed via commit b7216bd on origin/main (after rebase on bae00a1). The README Deployment section no longer claims a webhook-driven NodeHub deploy that does not exist; it now describes the actual state (no deploy workflow, no webhook, no NodeHub app) and points to manual-deploy and future-pipeline inputs. See `Dockerfile` and `.forgejo/workflows/ci.yml` for the build inputs any future deploy pipeline will need. -- triage-runner

Mark referenced this issue

2026-09-18 23:23:13 +00:00

Forgejo Actions CI never runs for planish — no runner covers the repo (repo_id=100) #16