fix(playout): point CasparCG log/data paths at writable /media volume

The 2.4.x server aborts at startup if its configured log-path isn't
writable/creatable. /opt/casparcg is a read-only-ish symlinked install
dir; the entrypoint already mkdirs /media/casparcg/{log,data}. Point the
config there to match (the working image used these paths).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Zac Gaetano 2026-05-31 14:11:00 -04:00
parent 739d08d4b5
commit abfbd034ab

View file

@ -2,8 +2,8 @@
<configuration> <configuration>
<paths> <paths>
<media-path>/media/</media-path> <media-path>/media/</media-path>
<log-path>/opt/casparcg/log/</log-path> <log-path>/media/casparcg/log/</log-path>
<data-path>/opt/casparcg/data/</data-path> <data-path>/media/casparcg/data/</data-path>
<template-path>/media/templates/</template-path> <template-path>/media/templates/</template-path>
</paths> </paths>