connman-gtk VS OctoPi

A bare minimum working version would be to install nm-connection-editor and have it start automatically on bootup. Then, when you detect that the window is closed and you have a network connection, open the browser. There aren't a lot of ready-to-go touchscreen friendly WiFi setup applications that aren't based around an applet, but if you have the option to use Connman instead of NetworkManager, you could look at connman-gtk as well, it seems pretty nice.

You can always find it on GitHub too.

OctoPi, the OctoPrint Pi distribution, uses mjpg-streamer by default and won't work with a Pi camera out of the box if you install a 64-bit OS version.

# out of the box: https://github.com/guysoft/OctoPi/issues

You can download the RC3 image from here: https://github.com/guysoft/OctoPi/issues/796. And use the RPi ImageReady to create the SD card.

I don't do any of that on my machines, I have github actions do that work anytime I change any of my scripts, or the source .img. If you're interested in the project, it is v1pi. This CustomPiOS is also used by Guy to maintain the official OctoPi image.

I run OctoPrint on a RockPi, but I also rolled my own embedded Linux distro (PrintNanny OS) to package this setup.

There are a lot of small papercuts, like OctoPrint using `vcgencmd` to measure CPU throttling. `vcgencmd` is part of Raspberry Pi's userland. Not a big deal (aliased to another util). I've also added WebRTC-based streaming to my build.

The recommended way to use OctoPrint is the OctoPi image, which is based on Raspbian / Raspberry Pi OS. The OctoPi image includes extras like haproxy and mjpg streamer for HTTP-based JPEG frame stream. If you end up baking a RockPi image, here's the OctoPi root file system for reference: https://github.com/guysoft/OctoPi/tree/devel/src/modules/oct...

OctoPi only goes up to version 0.18.0, so maybe you meant OctoPrint 1.7.2?

Might be related to this issue?