Notifies you when updates for the selected software is available.
- Bot Telegram notifications 🤖
- Easy deploy through Vagrant or Docker !
- Supports the following websites / services :
- Plex → Only the Synology NAS version for now.
- Synology DSM version → Downloads page
- pfsense → Downloads page
- Unifi cloud key → Downloads page
- Wordpress → Downloads page
- Easy integration as cronjob. If you want to monitor the cronjob, you can use healthchecks.
- Having Python 3 installed
- Having geckodriver installed in
/usr/local/bin/geckodriver(or edit the path in theSELENIUMvariable in thesettings.inifile)
- Rename the
settings.example.initosettings.ini - Edit the
settings.iniand add your credentials (more explanation regarding the variables below). - Edit the
installed.jsonand add the value of the exact version of the software you are currently using. - Run the following command to install the required modules locally
pip3 install -U -r requirements.txt --user
You could run this project in docker with a cronjob, so that the update checks are run once a day or once a week for example.
python3 update-notifier.py -i installed.json
NOTIFIERby defaulttelegramsince currently nothing else is supported.SELENIUMby default/usr/local/bin/geckodriversince that's where I decided to install it for docker and vagrant. If you install geckodriver manually you may have to adapt this path.HEALTHCHECKby default a random non-valid url. This is an URL that is to be pinged when the script was succesfully run. If you want to monitor the cronjob(s), you can use healthchecks.
BOT_TOKENPlease update this Token accordingly (more details below).CHAT_IDPlease update this ID accordingly (more details below). If you need help getting theBOT_TOKENandCHAT_IDvariables, please follow the *steps 1 and 2 in this gist
You can also deploy the project through docker or vagrant.
- Install Docker
- Run either
docker-compose upordocker build -t update-notifier -f deploy/Dockerfile .anddocker run --rm -d --name notify update-notifierif you want to use the Dockerfile directly. We are using the parameter--rmto auto-delete the container once it has sent the notification.
Important Note: Since the content of the repo is copied into the container, everytime you modify one of the files you will have to rebuild the image and start a container using that freshly built image.
- Install Vagrant
- Install virtualbox
cd deploy/vagrantto access the right foldervagrant upto start the virtual machine and the script
To destroy your Vagrant image:
vagrant destroy --force
If you encounter any issue with the setting up of the project, feel free to open an issue :)