feat: community one-click paths — "Deploy on Hostinger" button + Dokploy template (Coolify queued at 1,000 stars)

[vybe]

Summary

Add the two zero-cost community one-click paths that only need a pull-only compose file: a "Deploy on Hostinger" button (compose-URL + referral code) in the README/docs, and a Dokploy template PR to Dokploy/templates. Queue the equivalent Coolify service template for when the repo passes Coolify's 1,000-star contribution gate.

Context

Hostinger has no vendor program — its 1,000+ VPS/Docker templates are Hostinger-authored — but it publishes an open "Deploy on Hostinger" button: hostinger.com/docker-hosting?compose_url=<raw compose URL>&REFERRALCODE=<code> drops the user into Docker Manager on a KVM VPS with our compose pre-loaded (referral: 20% off for them, 20% of the sale back). Dokploy's catalog accepts PRs (compose + template.toml + logo; recent adds merged in 1–3 days) and already has 29 Docker-socket templates including OpenHands, the closest analog to Trinity. Coolify's catalog is the same idea but requires ≥1,000 GitHub stars (Trinity: ~460 at time of filing).

Both put Trinity one click away for anyone with a €8 Hetzner-class VPS — exactly the self-hoster the OSS front door serves. Depends on the pull-only hosted compose (#2280).

Acceptance Criteria

• "Deploy on Hostinger" button in the README + docs/DEPLOYMENT.md, pointing at the raw hosted compose URL on main; copy states KVM2 (8 GB) or larger — KVM1 is under the floor and the button cannot pin a plan.
• Referral code created and used in the button (owner: operator account); recorded where the team can find it.
• Dokploy PR opened and merged: blueprints/trinity/{docker-compose.yml, template.toml, meta.json, logo}; the docker-socket bind mount follows the OpenHands blueprint precedent; template verified from a Dokploy instance preview.
• Coolify service template drafted (templates/compose/trinity.yaml format, SERVICE_* magic vars) and parked with a note to submit at ≥1,000 stars.
• Both external listings added to a recurring audit (staleness check on the compose URL / pinned tags — buttons decay: Langflow, Cal.com, Dify all had dead deploy paths within a year).

Technical Notes

• Hostinger button docs: hostinger.com/support/deploy-on-hostinger-button/ ; Dokploy contributing: github.com/Dokploy/templates (CONTRIBUTING.md); Coolify rule: coolify.io/docs/get-started/contribute/service .
• Hostinger's Docker Manager lets users set env vars before deploy — keep required vars minimal and defaulted.

[obasilakis]

Ready to start, with one hard sequencing constraint (survey, 2026-09-11)

The dependency named here — the pull-only hosted compose, #2280 — has landed on dev, and the five images are public on GHCR (anonymous pull verified; per-image sizes on #2280). But both ACs that reference a public URL are un-satisfiable until v0.9.5 is cut to main:

1. GET /repos/abilityai/trinity/contents/docker-compose.hosted.yml?ref=main → 404. main is still 0.9.0; the hosted compose exists only on dev. The "Deploy on Hostinger" button takes a raw compose URL, and pointing it at dev would ship a button whose contents change under users.
2. There is no latest tag on GHCR — only 0.9.5-rc1, 0.9.5-rc2, v0.9.5-rc2 and sha-*, correct since only pre-releases have been cut. docker-compose.hosted.yml defaults to ${TRINITY_IMAGE_TAG:-latest}, so a Hostinger or Dokploy user pulling that file today gets a tag that does not exist.

So this ticket is genuinely cheap — a README/docs button URL plus a four-file PR to Dokploy/templates — but it cannot go out before the release cut. Do not work around it by pointing at dev or by pinning an rc tag in a public catalog entry.

Two things to settle while waiting:

• Pinned vs floating tag in the catalog entries. The Dokploy blueprint and the Hostinger compose both need a decision: latest (users get upgrades and occasionally a half-published release) or a pinned version (stable, but goes stale and needs a PR per release). The AC already asks for the staleness audit; the tag choice is the thing that audit is really watching, and it is worth writing down here before submission rather than after.
• Referral code owner. Recorded per the AC "where the team can find it" — the ent#464 precedent puts commercial/account detail on the private tracker, not on this public issue.

The 8 GB floor in the button copy is right and matters more here than anywhere else: Hostinger's button cannot pin a plan, and KVM1 is under the floor.