Any plans for a container image in the near future?

[davralin]

Eager to test this over other alternatives to ErsatzTV - but I need a container image to test.

Might not be something you want to prioritize this early on, but eager to test when that is available.

[jasongdove]

Thanks for the interest in the project. It's still super early, but I am interested in having someone (anyone other than myself) test things, so I'll get a docker image created and published soon.

The biggest issue is that, due to the reduced scope of this rewrite, there is no auto playout generation and the server requires a pre-generated playout for each channel. At this point I can probably include the ersatztv-playout-generator that I've been using for local testing along with some docker exec instructions on how to have it build a playout for the day, given a source folder of content.

[jasongdove]

Pushed to Docker Hub and GHCR, both with the develop tag:

ersatztv/next:develop
ghcr.io/ersatztv/next:develop

[jasongdove]

You can run the playout generator using a command like:

docker exec [container_name] /app/ersatztv-playout-generator --content-folder /media/test-movies --output-folder /config/channels/1/playout

Note that running it in docker like this will require the config folder to be mounted as read/write.

[jasongdove]

I also added a mode to sync a single channel's playout from ErsatzTV-legacy (note that this only works for local libraries):

docker exec [container_name] /app/ersatztv-playout-generator sync-channel --channel 1 --database /etv-legacy/ersatztv.sqlite3 --output-folder /config/channels/1/playout

[davralin]

Great, I have it deployed in kubernetes now, definitions are here

Works fine, I have it playing a Musicvideos-channel, by using the playout-generator against a folder of music videos.
Playout-generator runs as a sidecar to the regular deployment.

I do miss the XMLTV-part though, not that big of a deal with music videos, but obviously it matters for actual shows.

Not sure if that is out of scope, or just not there yet?

edit: oh btw, I'm also using an i915/vaapi-acceleration - so that's also a test complete, if you hadn't already tested that.

[jasongdove]

Ok - the latest builds will now generate XMLTV when new playout items are added, and will always serve XMLTV with at least the channel info. The data will be minimal, as the expectation is that a real scheduler will also generate the XMLTV, but it's better than having nothing at this point.

You will want to update your lineup config to add xmltv/folder (see https://github.com/ErsatzTV/next/blob/main/examples/lineup.json) and you will also want to change the way you run the playout generator so that it can load the folder and channel info from the lineup.json, like so:

docker exec [container_name] /app/ersatztv-playout-generator --lineup /config/lineup.json --channel 1 --content-folder /media/test-movies