Yet another windmill.

Buy a SAS adapter and put them in an external storage rack.

This hardware is for those who are storing EB of data.

I do it in sprints. I’ll set up a service, test it, get it working, then share it with the family.

I hear you on the instructions. A lot of these are pet projects that just happen to work well enough to share, so a bit of work is needed to implement them. If you document for others, you find that you can’t ever put every step in there because you can’t control all the variables.

Occasionally play two chirps together to make it sound like two devices and toast.

There appears to be many wireless options available. While there is no off the shelf option available, you may be able to automate connecting to the Wi-Fi of the cam and pulling the files from a Windows share. From there, you could put the files on a share for a service like photoprism.

If the only way up interface with it is through an app, and you don’t have an old smartphone to run the app, then you could consider running an android emulator.

Are you buying a cam or borrowing the same one? If you are borrowing again, you know the model? That will help us give better advice.

No shame in testing out enterprise solutions. Best of luck in your endeavor.

Oh, I see that RHEL has officially dropped docker support. You can try installing from binaries, but you are definitely striking out on your own here.

I don’t mean to rake you over the coals here, but what is the reasoning for sticking with RHEL for this project? If you are attempting to use it in an paid enterprise situation, you are better off sticking with items on the compatibility list. If you run into issues with other supported services, the first piece of advice will be to remove docker. Since your are not getting support for docker, I would advise running it from a supported OS.