Deployment

How to deploy

ALL FILE MUST REMAIN IN THE SAME DIRECTORY! Everything it does happens in the directory embyupdate.py lives in. If you move anything, delete anything, or rename anything, you're going to have issues. The script knows what directory it's in and behaves accordingly. You can move it anywhere, but you must move ALL FILES.

When EmbyUpdate updates itself, it does this for you. But the first time you may have to make the main script file executable.

Make the job executable by running this command on the script (optional)

sudo chmod u+x embyupdate.py 

Then you can run the script with a simple (optional)

sudo ./embyupdate.py

Or if you placed it in your $PATH (really optional! And untested)

sudo embyupdate.py

As stated before, you must either be root or use sudo because the script calls privileged Linux commands. I also highly suggest running the script through cron as root.

Example CRONTAB entry:

35 12   * * *    root  /usr/bin/python3 /path/to/embyupdate/embyupdate.py >> /path/to/embyupdate/embyupdate.log 2>&1

That runs the script every day at 12:35 and creates a log file in the location of my choice. I use my script location.

However, if your user has sudo access without a password, you could update the commands in the script by appending

sudo

in front of them. (I mean the SYSTEMD commands and the package install command). Then you could run the script as normal from your user.

./embyupdate.py

SYSTEMD METHOD (advanced but recommended)

(Wiki in progress)

There are two files in the directory called SYSTEMD. You can use these to set up a CRON-type schedule, but in SYSTEMD instead. I plan to have the app set this up for you one day. But that day is not today. I'll try to add a how-to here later, but for now, you can use those files and Google to set it up. It runs under SYSTEMD on my main server. Has been for years. Runs great.