FailedProxy
  • Joined on 2026-03-21
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 01:03:55 +00:00
a02b918ff9 Make the cancel actually remove the key it says it removed, instead of erroring into a swallowed stderr
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 00:50:12 +00:00
23825a824d Create the networks our own pushed templates name, instead of trusting a fresh mirror to have uncommented them
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 00:40:24 +00:00
cf67393db6 Read varaverk.cfg the way bash and the PHP side both read it, so a comment on the SCRIPTS_DIR line cannot disable cron suppression
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 00:32:15 +00:00
7ed0f5c23b Send the webhook setup to the path the partner actually uses, and arm the sync gates before the seed that depends on them
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 00:26:48 +00:00
f363c6cd55 Match the trigger failure patterns before the success one, since the failures echo a path back
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 00:25:55 +00:00
c8a6f58007 Launch owner-side Phase 2 through run_job.sh so it leaves a job record, and only claim it started once one exists
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 00:16:19 +00:00
93cdbaac57 Give the mirror the terminal step its half of phase 1 actually needs, instead of a button that cannot answer a password prompt
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-16 23:59:18 +00:00
47ad3b3075 Push the API key to the conf path the partner actually uses, and say so when there is no conf there
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-16 23:47:20 +00:00
1493cf2dcf Push our conf to partners on the 4-hour cycle too, since the conf-save hook the push half was written for never existed
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-16 23:40:51 +00:00
35e59d2510 Let the plugin read partner vars from the same RAM cache bash reads, so PHP and bash cannot disagree about a partner
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-16 20:14:30 +00:00
4f95cc6d13 Deliver master.conf to a node that has no Varaverk on it yet, which is the node that needs it
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-16 17:56:11 +00:00
f627658567 Read the partner's identity out of master.conf instead of asking for it again
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-16 17:54:06 +00:00
3c24550b19 Derive the pull target from the install location, so master.conf is safe to share between hosts
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-16 17:43:03 +00:00
98fab394a1 Resolve the partner through the shared Tailscale resolver, so a shared-tailnet peer is findable
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-16 17:31:25 +00:00
6fbc2b4125 Stop a missing SSH key making every Tailscale peer look like the Gitea host, and say so when the scripts are absent
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-16 17:24:28 +00:00
64de77c065 Let the setup checklist create the SSH key it is asking for, instead of linking to a guide
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-16 17:13:27 +00:00
19ba1e723c Stop a paused rsync counting as an absent partner and auto-offboarding the partnership
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-16 17:07:12 +00:00
1d4dc44668 Name HOST2 by the hostname the key derivation actually uses, not its Tailscale spelling
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-16 17:05:06 +00:00
0fe3435033 Let the conf push seed a node that has no master.conf yet, which is the node it exists to seed
FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-16 16:51:25 +00:00
6d9c856514 Open the sync gates when a partnership actually completes, instead of leaving them shut for ever