t5de/t5de-hub
2
0 Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases 1 Wiki Activity
35 Commits 2 Branches 2 Tags
36498b8a46ba300a1543716a406e74f060a55cbc
Commit Graph
6 Commits
Author SHA1 Message Date
dhkatzandClaude Opus 5.5 975e11e077 CI builds and pushes the images; Komodo only deploys
CI / test (push) Successful in 54s
Details
CI / image (apps/web/Dockerfile, t5de-hub-web) (push) Successful in 4s
Details
CI / image (apps/api/Dockerfile, t5de-hub-api) (push) Successful in 7s
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]>
 2026-10-31 15:53:10 +00:00
dhkatzandClaude Opus 5.5 7d20426d1b CI only tests again: Komodo builds and deploys
CI / test (push) Successful in 1m10s
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 e3770ceb57 Deploy with Komodo: main to staging, vX.Y.Z to prod
CI / test (push) Successful in 1m6s
Details
CI / deploy (push) Successful in 1m15s
Details 
CI now builds the API and website images after the tests, pushes them to git.t5de.dev, and deploys them through
Komodo (.gitea/scripts/deploy.py): pushes to main as :main to hub.staging.t5de.dev, vX.Y.Z tags as :X.Y.Z to
hub.t5de.dev, with the version pinned in t5de/t5de-infra.

The API image installs with --linker hoisted: Bun's isolated layout keeps the workspace links (@t5de/db) in each
package's own node_modules, which the image didn't copy, so the API couldn't start.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-30 08:16:05 -07:00
dhkatzandClaude Opus 5.5 7a06ba49c3 Rebuild the hub on Bun: Elysia API, Better Auth, Drizzle, Next.js website
CI / test (push) Successful in 30s
Details 
The hub becomes a Bun monorepo: apps/api (Elysia, Better Auth for accounts, roles, bans, proxy device
sign-in and JWT keys; tagline linking, presence and the console as before), packages/db (Drizzle; Postgres in
production, PGlite in development and tests), and the Next.js website from apps/web. Self-hostable with
docker compose; the website deploys to Vercel-style hosts, the API to any that runs Bun or containers. The
first version, in Go, is removed.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-29 05:03:54 -07:00
dhkatzandClaude Opus 5.5 7afada1c63 CI: test against a Postgres service (embedded Postgres won't run as root)
CI / test (push) Successful in 1m5s
Details 
Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-29 03:48:32 -07:00
dhkatzandClaude Opus 5.5 b9dc3f0ec1 Hub: accounts, IMVU linking by tagline, proxy sign-in, presence, console
CI / test (push) Failing after 42s
Details 
People sign up on the website and link IMVU accounts by putting a code in the account's tagline, which the
hub reads from IMVU's public API (the most recent proof wins; link caps per person). IMVU's age verification
or Access Pass make an account adult. T5DE's proxy signs in with a device code and keeps a WebSocket open,
reporting the IMVU account in use and the community products it wears; /online shows those who opted in.
Moderators get a console: who's online, people, link caps, bans, roles, and the audit log. Tests run the
website and API against an embedded Postgres and a fake IMVU API.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-29 03:45:52 -07:00