The point of different licenses is the thing you ought to be looking at.
The point of mit is to get the licensed thing used as widely as possible. It breaks down any barriers to use. A good example of something that should be mit licensed is an encryption algorithm. A good example of something that shouldn’t be mit licensed is anything else.
The point of bsd3-clause is to prevent the licensed likeness from being used to imply the creator shares some view or idea. A good example of something that should be bsd3-clause licensed is the royalty free music on youtube. A good example of something that shouldn’t be bsd3-clause licensed is a creative work the author wants to have their name known for.
The point of the various gpl licenses is to create a digital commons that all people can access. A good example of something that ought to be gpl licensed is a game engine you want people to be able to freely use and modify but never make secret changes to sell. A good example of something that shouldn’t be gpl is a game engine you want to eventually sell the code of or make secret changes and sell the code of those.
If my language sounds biased, it is because I have a bias.
YOU SHOULD NOT RUN YOUR CAMERA SERVER ON YOUR DOCKERPILE HOMELAB BOX THATS HOSTING 69 DIFFERENT THINGS!
If you have the time to set it up, learn the different use cases of cameras and monitor it for failure somehow then frigate is good.
If you’re using ip cameras you 100% no foolin without question have to put them on a vlan at the very least. They are an insane liability when it comes to network security.
If I had it all to do over again I’d have done power over ethernet, put them all on their own switch that does poe injection and done vlan by the one phy going from the poe switch to the router.
People will fight me about this, but ip cameras are all pretty much the same. They make available some video stream at a preset bitrate and resolution, use built in infrared or visible lighting and offer pan, tilt and zoom (ptz) controls to authorized users. Some have motion detection and object recognition on device which may or may not be surfaced to the camera server.
I always offload object detection and classification to the server even if the camera has it on board because even on cpu image inference is “okay” and with an old gt750 nvidia card you can do much faster object detection and classification. The reason for doing it all on server is in order to get consistent results.
If you are a computer savvy person: congratulations, you picked a project that uses memory, gpu and disk space at a time when they’re all at a premium! Hell yeah!
YOU SHOULD NOT RUN YOUR CAMERA SERVER ON YOUR DOCKERPILE HOMELAB BOX THATS HOSTING 69 DIFFERENT THINGS!
Fortunately you don’t need ddr5 for this so any old server is fine. Scale your ram needs up or down depending on the cameras you’re looking for.
Consider buying one of those ten year old servers with redundant power supplies. Even if they’re both connected to the same ups (and you need the camera server on it’s own ups) you can keep going when one dies.
There are two minds regarding disks in surveillance servers. The first is “fuck it, kill the disks, who cares, they’re a wear part!” The second is “no, careful management of our disks will ensure trouble free use for years to come.” I’m of the second variety and run a zpool of small (<2tb) disks with an optane cache. The cache saves the disks from some of the drive killing random writes and reads and lets me keep running at speed when reviewing things.
When you go to put in an old gpu, make sure the plastic cowling shaped like an anime titty isn’t too big otherwise the pcie standard sized spaces in most servers won’t be able to take it.
YOU SHOULD NOT RUN YOUR CAMERA SERVER ON YOUR DOCKERPILE HOMELAB BOX THATS HOSTING 69 DIFFERENT THINGS!
I have been robbed and had to hand camera data over to the cops and can offer you some more practical advice if you’re open to it.