FailedProxy

0 Followers · 0 Following

• Joined on 2026-03-21

Repositories

1

Projects Packages Public Activity Starred Repositories

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 19:10:33 +00:00

e8ee5b052b Failover Coverage and Shared Services pickers on the Partnership page

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 19:09:16 +00:00

d7980da35e vv_docker_containers lives in common.php, not docker.php

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 19:08:45 +00:00

239e100b44 Partnership page: Varaverk assistant profile, row-2 Actions, and the two container list cards

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 18:52:23 +00:00

2216072669 Drop the Host Settings card now the partnership settings card covers HOST1/HOST2

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 18:46:20 +00:00

8cf3ff31db Show the partner's API key and whether it is answering on the remote card

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 18:45:39 +00:00

b108a6fe62 Report the partner's API key and whether it is actually answering

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 18:43:06 +00:00

f58ff68ab3 Mesh partnership leg reads this host's own state file, not one named after the remote

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 18:42:17 +00:00

e7e9d9fecf Green mesh banner on each remote card, naming the failing leg when it is not green

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 18:41:37 +00:00

d417bd5360 Match the tailnet device name to the conf hostname by unambiguous prefix

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 18:38:06 +00:00

90f3b0b7da Put the assistant on the Partnership tab

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 18:36:23 +00:00

bce3bf61e9 Partnership page: one settings card instead of three, and a Data Transferred card

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 18:13:19 +00:00

49372996ac Wire the folder-layout mirroring into onboard Step 12

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 18:08:36 +00:00

e3ed5a53f2 Reproduce the owner's docker folder layout on the mirror instead of one lump fallback folder

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 17:47:21 +00:00

1231cd69a8 A host with the VM service off is not a host with a broken API key

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 17:45:29 +00:00

8e85a67e7b One faint Skip in the corner; the completion card owns the real exits

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 17:06:48 +00:00

1badb93331 Make the onboard-in-progress state survive a page reload

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 16:25:18 +00:00

e23358ea0c Tell the mirror that Phase 2 is running instead of leaving it on a greyed button

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 16:13:54 +00:00

73bbae14c1 Stop resolve_remote_scripts_dir silently returning the local path as the partner's

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 16:12:11 +00:00

74e3b8b067 Resolve docker_network_connect.sh on the mirror, and give the wizard poll time to outlast Phase 2

FailedProxy pushed to main at FailedProxy/Varaverk 2026-08-17 15:57:47 +00:00

9a1254048e Match the WebUI template by its XML Name element, and count the final sync on rsync's actual exit