Tooling in container to make the changes of #1616 work

[alexanderadam]

Maybe a Q&A discussion is better for this than my comment on the closed issue 😉

In order to make the GitHub decoupling actually work on gitea/forgejo, the Dockerfile would need to have the tea binary available, right?
Is this coming with another PR?

EDIT: I submitted a PR for this.

[lMysticl]

Yes. On current main, the Gitea/Forgejo implementation and the stock container image are out of sync.

gitea-service.ts resolves tea with findExecutable("tea"); when it is absent, the service raises TeaCliMissingError. Host probing and authentication also call tea login list -o json. The base image installs Git, curl, and the other runtime tools, but it does not install tea.

So the adapter code can be present in the image while Gitea/Forgejo authentication and operations remain unavailable. I cannot confirm whether another PR is planned, but the dependency is not present in the current Dockerfile.

The container-side fix should install the correct tea binary for each target architecture in /usr/local/bin, verify it during the image build, and keep its login configuration under the existing XDG_CONFIG_HOME=/home/paseo/.config. Until that is added upstream, a small derived image that adds tea is the practical workaround.

References: tea resolution and missing-CLI error, runtime lookup, and the current container package list.

[alexanderadam]

Instead of adding the binaries, I submitted a PR to allow them to be installed without having to rebuild the image.