• 0 Posts
  • 364 Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle




  • APIs. Or the ends are achieved by sharing data between apps in common data storage. But I prefer to be a tourist in my infrastructure, I no longer hand-bomb changes to systems.

    My design pattern is essentially to integrate more and more of the container creation into config. Right now I’m using ansible and it’s nice. More automation means troubleshooting has fewer variables.

    I had issues yesterday with a package upgrade across several containers, and it ended up being two config changes. I cycle the apps and done. That’s it.







  • Frigate is popular.

    I used to use ZoneMinder, it worked well, but you must be very familiar with onvif, primary/secondary channels, and key frames for it to work well.

    I only switched to frigate because of the person/animal detection. It’s ok, but it does need some polish in a few areas like event retention, and it could stand some more approachable documentation.









  • Portability is not really an aspect one needs to consider when it comes to a NAS

    Hard disagree, and it is one of the best things about ZFS. You can plunk a ZFS pool on another system and be almost certain it will import. Systems die. Having been through several data-loss incidents, I find it is much preferable to be able to pull 1 disk than have to drag out 2 or three to transplant a ZFS pool.

    Regarding the scrubs, I was trying to indicate that ZFS is more than just a raid manager, there are advantages to ZFS on even a single disk.

    for a home NAS, the goal is maximising data storage capacity without a major hit on performance

    If that were entirely true, striping would be the most popular ZFS pool arrangement, since you get performance and max storage.

    Edit: this was not to say “you’re wrong”, just different approaches to storage.