MichaIng

> I moved the monitoring info to a second column which only appears if needed. I indeed meant a "column", not a "row" what you added now. So basically switching...

Jep, basically that. If possible, `0.43.1b1` would be great as beta version string, since this is the one we use/the schema we need to use for the Python package on...

Great work! Let's do the cleanup right away. We have this PR as reference and the commits you referenced for the obsolete variables/functions remain visible here. I'll do a final...

Ah yes that looks great. We use this `docker/metadata-action` in our workflow already. But I did not have a closer look into it, about how to pass the version tags...

Currently it fails loudly, but effectively those failing tags/types are just skipped. So it would work to just add a `type=ref,event=tag` (if I see it correctly), to have a Docker...

> My idea was to remove the pull request and push from [here](https://github.com/motioneye-project/motioneye/blob/main/.github/workflows/docker.yml#L3) and replace them with tags. This will work if we are going to use tags for releases...

If this is on a Raspberry Pi, and KMS is enabled (`dtoverlay=vc4-kms-v3d` in `/boot/config.txt`), then it fails expectedly. If it is a camera module 3 or newer, then it cannot...

> Use care in selecting the right directions because a misstep will break the process. I ended up starting over with a fresh install of bookworm because I messed up...

Do you remember the error you faced, and at which step exactly? In case of the dependencies, the 32-bit instructions contain just less dependencies, so installing the ones for 64-bit...

Python does not seem to have a native autoreload feature, which would be required here. I tend to just restart motionEye when testing changes: ```sh systemctl restart motioneye ```