Files

T

admin b3eabfd611 catalog: re-pin wanderer to the current upstream shape, retire plant-it, add the resolvability gate

wanderer: ghcr.io/flomp/wanderer:0.16.0 is a ghost - upstream split the app
into web+db images, moved registry and renamed the org. Restructured to
upstream's own v0.20.0 compose (3 services, new /data/plugins volume, second
public hostname for PocketBase, meilisearch pinned DOWN to upstream's v1.36.0
per the R-42 ruling).

plant-it: retired. The repo name was wrong (plant-it-server) but upstream has
DELETED self-hosting; last server image is 2024-12-10 and it needs MySQL+Redis
the template never had. Moved to retired/ rather than deleted - reversible.

R-41 slice 1: check-image-resolvable.py. Encodes two traps - manifest inspect
exits 0 while printing toomanyrequests, and the inverse, where the first sweep
called 24 of 65 pins dead because Hub throttled it. Ambiguity is INCONCLUSIVE,
never an accusation.

2026-07-21 15:30:15 +02:00

plant-it

catalog: re-pin wanderer to the current upstream shape, retire plant-it, add the resolvability gate

2026-07-21 15:30:15 +02:00

README.md

catalog: re-pin wanderer to the current upstream shape, retire plant-it, add the resolvability gate

2026-07-21 15:30:15 +02:00

README.md

Retired templates

Apps that were removed from templates/ and are therefore no longer offered to customers.

The controller discovers apps by directory name under templates/ (internal/sync/sync.go copyTemplates), so anything here is invisible to the catalog sync. The files are kept rather than deleted so a retirement is reversible: git mv retired/<app> templates/<app> puts it back, and the full history of the template is intact either way.

Note on boxes that already synced the app: the sync only ADDS and UPDATES — it never removes a stack directory it previously copied. Retiring a template therefore stops it being offered to NEW boxes and freezes it on existing ones; it does not reach out and delete anything. For every app retired so far this is moot, because none of them was ever successfully deployable.

App	Retired	Why
`plant-it`	2026-07-21	Upstream discontinued self-hosting. The pinned `msdeluise/plant-it:0.10.0` never resolved because the image repository is `msdeluise/plant-it-server` — but fixing the name was not the real answer. The `backend/` and `deployment/` directories have been DELETED from upstream `main`; the project is now an Android app distributed via F-Droid/Obtainium, with a maintainer note that active development has slowed. The last server image, `msdeluise/plant-it-server:0.10.0`, was pushed 2024-12-10 and is a security-frozen Spring Boot 3.4.0. It also requires MySQL 8.0 + Redis, which the template never had — its header claimed "Database: None (file-based)", which was wrong from the start. Operator ruling 2026-07-21: do not ship unmaintained software to customers. Revive only if upstream restores a maintained server edition.