coexistence hardening for a shared VPS — oom_score_adj, deploy docs, backup prune hardening - #33
Merged
Merged
Conversation
…off doppel's CLAP on a shared box
…-proxy rule, box-user split
…rue that masked rm failures
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prep for a second app coexisting on the same Hetzner box. Biases the OOM killer away from doppel's CLAP-holding app/worker (
oom_score_adj: -500) so a co-tenant's unbounded build spike can't knock them out, and documents the multi-tenant boundary in DEPLOY.md — the co-tenant's public Caddy edge never proxies doppel's loopback API, and the two run as separate Linux users with separate crontabs and R2 remotes. Also hardens the backup retention prune across two review rounds: it fails closed on a realrmerror, an unreadable backup dir, or a stuck local prune rather than masking failures behind a green healthcheck, and prunes from an explicitly-sorted nullglob array so deletion order never depends on the shell's glob sort.