t5de/t5de-catalog
2
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
4 Commits 1 Branch 1 Tag
f60ba346f8f6b850a800c98405d52a265fe59d10
Commit Graph
4 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
dhkatzandClaude Opus 5.5 f60ba346f8 CI builds and pushes the images; Komodo only deploys
CI / build (push) Successful in 8s
Details
CI / image (push) Successful in 22s
Details 
After the tests pass, main pushes :latest-main and :main-<commit>, and vX.Y.Z tags push :X.Y.Z, :X.Y and
:latest to git.t5de.dev (registry login: the t5de org secret REGISTRY_TOKEN). Komodo deploys them once the
ref's CI has passed; it no longer builds.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
v0.1.0 		2026-10-31 15:53:10 +00:00
dhkatzandClaude Opus 5.5 576b26cf81 CI only tests again: Komodo builds and deploys
CI / build (push) Successful in 21s
Details 
Komodo now watches the t5de org (Gitea webhook → its t5de-push action, defined in t5de-infra): it builds and
deploys a commit to staging once this CI passes on main, and to prod for vX.Y.Z tags. So the deploy job and
.gitea/scripts/deploy.py go, and this repo no longer needs to know how it's deployed.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-30 15:47:58 +00:00
dhkatzandClaude Opus 5.5 715c0bd0d7 Deploy with Komodo: main to staging, vX.Y.Z to prod
CI / build (push) Successful in 14s
Details
CI / deploy (push) Successful in 37s
Details 
CI now pushes the Docker image to git.t5de.dev after the tests and deploys it through Komodo
(.gitea/scripts/deploy.py): pushes to main as :main to catalog.staging.t5de.dev, vX.Y.Z tags as :X.Y.Z to
catalog.t5de.dev, with the version pinned in t5de/t5de-infra.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-30 08:09:15 -07:00
dhkatzandClaude Opus 5.5 8742829e77 t5de-catalog: store and serve community product files
CI / build (push) Successful in 54s
Details 
A Go server that takes product uploads with hub upload tokens, checks them by
t5de-api's pack rules, stores files by sha256, registers revisions with the hub
(POST /api/v1/catalog/revisions), and serves files with immutable caching;
files used only by adult revisions need an adult access token. Contract:
t5de-hub's docs/products.md.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-29 18:59:16 -07:00