extant2000/flamenet-relay
1
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases Wiki Activity

Hand the runner cache timer to the infra repo #206

Merged
paulhitt merged 1 commits from chore/hand-the-runner-cache-timer-to-infra into main 2026-09-12 20:41:36 +00:00
Conversation 1 Commits 1 Files Changed 3
-72
paulhitt commented 2026-09-12 20:14:10 +00:00 (Migrated from gitlab.com)
Copy Link
Copy Source

Housekeeps the GitLab runner's build cache, which is not part of the relay. This repository is public and about a messenger server, so it now lives in hitthosting-infra beside the restic and nzbdav timers: paulhitt/hitthosting-infra!3.

What remains under Scripts/monitoring/ is the messenger's own: health, the two privacy checks, and the database vacuum.

The one cross-repo tie, and why it is fine

messenger-health.sh stays here and still calls /srv/prod/monitoring/prune-runner-cache.sh when /data crosses 93 percent. That is a path on the box, not in this tree, so which repository ships the script does not reach it. The call is already guarded:

&& [ -x /srv/prod/monitoring/prune-runner-cache.sh ]; then

so it degrades to not sweeping rather than erroring, if the script is ever absent.

Order: hitthosting-infra!3 should land first, so the script is never in neither repository. Nothing on the box changes either way; both repositories deploy to the same /srv/prod/monitoring/ path.

🤖 Generated with Claude Code

Housekeeps the GitLab runner's build cache, which is not part of the relay. This repository is public and about a messenger server, so it now lives in hitthosting-infra beside the restic and nzbdav timers: paulhitt/hitthosting-infra!3. What remains under `Scripts/monitoring/` is the messenger's own: health, the two privacy checks, and the database vacuum. ### The one cross-repo tie, and why it is fine `messenger-health.sh` stays here and still calls `/srv/prod/monitoring/prune-runner-cache.sh` when `/data` crosses 93 percent. That is a path on the box, not in this tree, so which repository ships the script does not reach it. The call is already guarded: ```sh && [ -x /srv/prod/monitoring/prune-runner-cache.sh ]; then ``` so it degrades to not sweeping rather than erroring, if the script is ever absent. **Order:** hitthosting-infra!3 should land first, so the script is never in neither repository. Nothing on the box changes either way; both repositories deploy to the same `/srv/prod/monitoring/` path. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
paulhitt (Migrated from gitlab.com) scheduled this pull request to auto merge when all checks succeed 2026-09-12 20:19:24 +00:00
paulhitt (Migrated from gitlab.com) merged commit 4e88841a06 into main 2026-09-12 20:41:36 +00:00
paulhitt commented 2026-09-12 20:41:37 +00:00 (Migrated from gitlab.com)
Copy Link
Copy Source

mentioned in commit 4e88841a06

mentioned in commit 4e88841a0695152ac1f6291b59cf9cd50ccc8e1d
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
accuracy
A public page claims something the code does not do
 architecture
blocked:apple
Waiting on App Store review
 bug
ci
deploy
docs
federation
hardening
idea
investigation
ops
Deploy, CI, infrastructure
 parity
One platform has it and the other does not
 planning
privacy
Changes what is stored, or what we say is stored
 reliability
scalability
security
self-hosting
signup
stability
tech-debt
tooling
unwired
Built in the engine, not reachable from the UI
 verification
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
extant2000git
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: extant2000/flamenet-relay#206