Update to MotionEye

It has been containerized and it is considerably faster.  This may be because I am using a Pi3 in a case as my base unit. I have seen some stories and they did not make me feel good about the Pi layout due to processor heat.  I have containerized with one of my photon instances, and the image pulled was a newer version of MotionEye, but an older version of Motion.  Streaming rate increased by 10-20x.  The capture rate was at least doubled.

Keep in mind that this may be a stopgap measure until I have the nerve to create a secure tunnel to a cloud in order to perform the motion capture there, then drop it into cloud storage.  Let's also be honest, I will probably be going towards an Amazon cloud solution to host it on.  I'm not on expert on the higher math type of programming that is required in order to make a universal cloud solution that you can simply turn on like a service, but I will put up a post explaining my poorly designed process when I get around to it.

Until then, let's get this upgrade going.  For Portainer users, create a motioneye volume and motioneyelib volume.  You should be able to start building the container immediately after.  If you have an existing MotionEye Pi that you want to scrape the config from, hit the Backup button in the General Settings, then continue with the following Aggregate.  I will validate the upgrade capability in the container over the next couple of months and either blog about how to pull an update, or that the update occurs automatically when restarting the container (if you have it set to always pull new).

Aggregate 1
Docker install instructions for MotionEye

I've edited this to make sure that you know not to upload the existing configuration from a Pi.  It will break it.  But, you can take a look at the tarball that you pulled from the Pi for all of your settings.
EDITED OUT --> Once installed, Restore the backup in the General Settings menu if you have one. <--  Keep in mind that you will need to add the ports for streaming as described in the Aggregate.  If you want to see something really neat, if you left the old Pi instance running, turn it off and pay attention to the streaming rates on your cameras.  Should add another 10-30% boost to their new streaming rate.  My latest and greatest version of the Pi camera is at an average of 30fps streaming.

We will need to modify the File Storage parameters to save to persistent storage.  You can create a directory in one of the previously created volumes, or you can upload.  I will probably set the system to upload and be done with the local storage for anything older than a day.  Another point of honesty here, if someone breaks into my house, they will probably take anything technology related.  Leaving the videos on local storage is not a great idea.

Looking forward to digging around more, I just need to figure out how to rename it from a UUID to something I can toss into a DNS server.  I will have some more updates in the future about best practices that I find.