FailedProxy/Varaverk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove point-in-time HOST2 status from the codebase

Browse Source 
Comments asserting a partner is down, being rebuilt or not yet installed are true on the day they are written and wrong afterwards, and nothing prompts anyone to revisit them. Behaviour is described generically; current state belongs in operator memory, not in tracked files.
This commit is contained in:
Gmer4Lfe
2026-08-17 15:20:25 -04:00
parent e8ee5b052b
commit 0447fa6f86
11 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -2
View File
@@ -77,8 +77,8 @@ and tested but currently switched off:
```
FALLBACK_ENABLED=true ← running
PARTNERSHIP_ENABLED=true ← running
RSYNC_ENABLED=false ← off until HOST2 is back
CONF_SYNC_ENABLED=false ← off until HOST2 is back
RSYNC_ENABLED=false ← global rsync gate
CONF_SYNC_ENABLED=false ← partner conf caching
```
Everything here is built and audited. The two-server half is waiting on the second server.