515a864ef0
The previous commit fixed the target catalog and the operator alarm, but the actuators the catalog invokes carried the same E: paths. Idunn would have resolved every target and then failed on the first restart or deploy it ran, for exactly the reason the alarm failed. Rebased 41 references across 27 scripts: - .cmd bodies invoke their sibling .ps1 through %~dp0 instead of an absolute drive path, and restart-weksa.cmd reaches its sibling repo the same way. - .ps1 parameter defaults and assignments derive from $PSScriptRoot: one level up for paths inside Odin, two for sibling repos under the projects root. Left deliberately alone: $RemoteViliRoot and $StateRoot in restart-vili.ps1. Both are consumed inside the EncodedCommand block that restart-vili ssh's to raven, so they describe raven's filesystem, not starfire's. Whether raven also moved off E: is an operator question, not something to infer from here. Verified: all 46 scripts under scripts/ parse clean, and the derivation resolves to F:\Projects\Odin and F:\Projects on this host. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
10 lines
409 B
Batchfile
10 lines
409 B
Batchfile
@echo off
|
|
if not "%IDUNN_ACTUATOR%"=="1" (
|
|
echo This deployment wrapper is an Idunn actuator. Configure Idunn; do not deploy manually.
|
|
exit /b 1
|
|
)
|
|
if /I not "%IDUNN_COMMAND_AUTHORITY%"=="idunn-daemon" (
|
|
echo This deployment wrapper is an Idunn actuator. Configure Idunn; do not deploy manually.
|
|
exit /b 1
|
|
)
|
|
powershell.exe -NoProfile -ExecutionPolicy Bypass -File %~dp0deploy-yggdrasil-repixelizer.ps1
|