Drop the PORT=3000 override from the quadlet so the container listens
on PORT from config.env like the native service, and publish
127.0.0.1:3128:3128. Move PublishPort into a %config(noreplace) quadlet
drop-in, /etc/containers/systemd/turborepo-remote-cache.container.d/
publish-port.conf, so hosts can change the host binding without an
untracked override. Document in config.env that the container
overrides HOST and that the listen address belongs in PublishPort.
Upstream joins STORAGE_PATH onto os.tmpdir() unless
STORAGE_PATH_USE_TMP_FOLDER=false, even for absolute paths, so the
container wrote artifacts to /tmp/app/cache instead of the bind mount
and lost them on every restart. Set the flag in both config.env
(native service) and the quadlet, and chown the host cache dir to the
container user via the :U volume option.
- Source0 now points at the GitHub tag tarball so spectool -g can
fetch it; drops fetch-sources.sh
- %build runs pnpm install --frozen-lockfile --ignore-scripts, then
pnpm exec tsc (bypasses upstream lint), then pnpm prune --prod
- Guard all -service bits behind %bcond_without service so offline
builds can produce base + -container with --without service
- Base and -container subpackages never need network
Self-hosted Turborepo remote cache server packaged as a Fedora RPM
with the same base + -service + -container split used by the gitea
package.
- Base: dynamic sysusers turbo-cache user, /etc/turborepo-remote-cache
config dir with config.env token template, /var/cache storage dir
- -service: native Node.js systemd unit, app installed to
%{nodejs_sitelib}/turborepo-remote-cache with pnpm-vendored
production node_modules (built via fetch-sources.sh)
- -container: Podman quadlet pinned to
docker.io/ducktors/turborepo-remote-cache:2.8.2
- Listens on 127.0.0.1:3128; runners reach via host.containers.internal
zpericic