> Zoneminder in particular is (or was, anyway) an absolute nightmare to deploy and run. Install it, configure it, make sure to give it enough storage so you ha

> Zoneminder in particular is (or was, anyway) an absolute nightmare to deploy and run. Install it, configure it, make sure to give it enough storage so you have the desired retention duration - here about 2 days - and restart it regularly to keep memory leaks in check. Once you've got it set up don't mess with it anymore. I've run it this way for close to 5 years now without too many problems. I did a thorough survey of the available free and cloud-free software before I settled on ZM and regularly check whether something 'better' has shown up but have not seen anything which matches the functionality yet. There's lots of other surveillance camera software but most developers seem to consider a Javascript-heavy glitzy UI the prime directive while the backend is more of an afterthought. I hardly ever use the UI, most interaction goes through apps (ZMNinja etc.) or other systems (OpenHAB etc.). ZM, once configured, does very well this way as long as you keep the memory leaks in the zmc processes in check. In short ZM is a flawed but functional piece of software with the best balance between functionality and flaws for our application - stable and farm monitoring services. It may not be what your want if you want to have a web interface to that camera on the front porch.