Just did it again on a Pi2 with the original PiCamera and a WiPi USB WiFi dongle.
Here are the steps in the order I did them, logged in as user pi to install Motioneye on Raspbian-Stretch:
//Get the latest Raspbian stretch upgrades:
sudo apt-get update
sudo apt-get dist-upgrade
// add v4l2 driver for picamera, you can skip this if only using USB webcams or netcams
sudo nano /etc/modules
// add, after i2c-dev:
bcm2835-v4l2
// extra packages from the standard repos:
sudo apt-get install libssl-dev libcurl4-openssl-dev libmariadbclient18 libpq5 mysql-common ffmpeg
// get and install pre-built motion package for stretch:
sudo dpkg -i pi_stretch_motion_4.0.1-1_armhf.deb
// install motioneye
sudo pip install motioneye
// initial setup of config files and motioneye deamon:
sudo mkdir -p /etc/motioneye
sudo cp /usr/local/share/motioneye/extra/motioneye.conf.sample /etc/motioneye/motioneye.conf
sudo mkdir -p /var/lib/motioneye
sudo cp /usr/local/share/motioneye/extra/motioneye.systemd-unit-local /etc/systemd/system/motioneye.service
sudo systemctl daemon-reload
sudo systemctl enable motioneye
sudo systemctl start motioneye
// restart the system
sudo reboot
Connect your browser to port 8765, use Chromium on the Pi as localhost:8765 or on a different machine on your local network yourPi_IP:8765
My router automatically adds dhcp clients to its caching DNS so I can use the Pi2 hostname to connect: picam:8765
Configure to suit.
Hope this helps someone.
My reason for doing this is to see if a different WiFi subsystem can stay up for 24/7 usage. The PiZero-W (and Pi3) apparently can't with current firmware for the chip used, see:
If it works, next week I'll disable the PiZero-W WiFi and try the WiPi dongle with it, not optimum solution, but I've other plans for the Pi2 using a wired connection. I got the PiZero-W to use with either something like Motioneye or some of my own code to capture images on command After trying Motioneyeos on the Pi2 with a wired connection.