env file for docker-compose: sudo vi /opt/dockerfiles/deepstack/.env The first step is to create a "home directory" where DeepStack will like: one for the docker-compose.yml file, the other for the DeepStack storage directory.Ĭreate the initial directories: sudo mkdir -p /opt/dockerfiles/deepstack/Ĭreate the initial. You'll need two components, docker and docker-compose, to get this deployed. This Docker server is where we'll be running the DeepStack container. Keep in mind that I'm assuming that you already have a server running Docker. This guide will walk you through the configuration steps. Instead, I'm going to be running DeepStack on my Arch Linux Docker server that has some free resources. You could technically have Blue Iris side-by-side with DeepStack on the Windows server if you've got enough horsepower for both. Now, there is a version of DeepStack that runs on Windows. Each Blue Iris camera has configurable settings around the types of DeepStack detection too. Blue Iris will detect generic motion, pass it to DeepStack for further analysis, and DeepStack will let you know if there's an actual person, bike, vehicle, etc in the video capture that's being analyzed. I don't care about the generic motion alerts.Įnter DeepStack for object-based detection, which has recently been incorporated into Blue Iris. Me? I just want to get alerted on certain objects like people, cars, and the occasional bicycle. You'll get alerts on shadows, trees moving, cars driving, by etc. However, the downside is that it's robust motion detection is just that: motion detection. It's relatively easy to configure, supports a ton of cameras, and constantly adds new features. I'm a fan of Blue Iris for security camera recording.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |