The image never built: CASPAR_URL pointed at a v2.3.3-stable Linux tarball that CasparCG never published (2.3.x is Windows-only; Linux builds start at 2.4.0, and 2.4.1+ ship only as .deb). Rewrite to install the 2.5.0 noble server + CEF debs on an ubuntu:24.04 base (Node 20 via nodesource), letting apt resolve the GL/ffmpeg/openal runtime deps. Binary install dir is discovered from the deb file list and symlinked to /opt/casparcg so the entrypoint + config still run from there. Move CasparCG log/data dirs to /media (writable mount) since the install dir may be read-only. NOT runtime-validated: the 2.5 casparcg.config schema and the AMCP consumer syntax (ADD <ch> STREAM/FILE) were authored against 2.3 and must be smoke- tested against 2.5 before a channel start can be trusted. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
29 lines
873 B
XML
29 lines
873 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<configuration>
|
|
<paths>
|
|
<media-path>/media/</media-path>
|
|
<log-path>/media/casparcg/log/</log-path>
|
|
<data-path>/media/casparcg/data/</data-path>
|
|
<template-path>/media/templates/</template-path>
|
|
</paths>
|
|
|
|
<!-- Single logical channel. The output consumer (DeckLink / NDI / SRT / RTMP)
|
|
is added at runtime over AMCP by the Node shim (playout-manager.js), so no
|
|
static consumer is declared here. A screen consumer is intentionally
|
|
omitted — this is a headless server. -->
|
|
<channels>
|
|
<channel>
|
|
<video-mode>1080i5994</video-mode>
|
|
<consumers>
|
|
</consumers>
|
|
</channel>
|
|
</channels>
|
|
|
|
<controllers>
|
|
<!-- AMCP over TCP — the Node shim connects here. -->
|
|
<tcp>
|
|
<port>5250</port>
|
|
<protocol>AMCP</protocol>
|
|
</tcp>
|
|
</controllers>
|
|
</configuration>
|