[FEATURE] Published docker containers

Problem

Every release I still have to build the containers myself, which apparently doesn't always work the way it is supposed to go. I'd really love to start using OpenCut, but ideally selfhosted. This now becomes quite difficult since i don't know why builds are failing and have no intention of modifying local code to do that each time a new release is published

Solution

Since there now is a release cycle, wouldn't it be cool to have a containerized setup available? Where you have a quick setup guide and it pulls containers from ghcr or something so deployment gets a lot easier? You can add this to a github action that creates and updates the packages / containers on every new release and you would control the building process to work instead of having to deal with our local issues.

Alternative

An alternative would be to have this staying the same way, and keep trying to build it locally.

Anything else?

I really like this project! Much respect for everything that is done so far and I cannot wait to start using this locally!

Start by reviewing the repository's existing release process and local container build instructions. Define the GitHub Actions and GHCR setup needed to publish containers on each release, plus a quick self-hosting guide. Done means a released container can be pulled from GHCR and deployed without rebuilding local code.