Portainer Templates logo

Portainer Templates

Change Detection Change Detection

Container

Network

Self-hosted website change detection monitoring.
Source: https://github.com/dgtlmoon/changedetection.io

Image details

Pulls: 11.4M
Architecture: amd64, arm64, arm/v7, arm/v8
Image size: 371 MB
Latest: 0.60
User: dgtlmoon
Created: Jan 28, 2021
Updated: 1 day ago
Status: active

Source details

Repo: dgtlmoon/changedetection.io
Stars: 34.7k
Forks: 2k
Language: Python
License: Apache-2.0
Latest: 0.60.8 · 2 days ago
Updated: 2 days ago
Website: changedetection.io/

Configuration

Type
Container
Platform
linux
Image
dgtlmoon/changedetection.io:latest
Volumes
/datastore : /portainer/Files/AppData/Config/changedetection
Restart
always

Template by xneo1

Standalone Install

Select an install method, to see config/commands for deploying Change Detection

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Change Detection, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation, or see dgtlmoon/changedetection.io for app-specific guidance.

Web page change monitoring, the best way to monitor website changes, restock alerts - Get notifications when a page changes via via Discord, Telegram, Slack, Email, NTFY and 85+ more

Welcome to changedetection.io!
With changedetection.io you can monitor thousands of websites for changes with ease, Use the Visual Selector to select only parts of the webpage of interest, use the builtin Browser Steps tools to interact with the web page, such as search queries, job searches, change detection from behind logins and many more use-cases.
The built-in product restock alert plugin will let you know when a product is no longer "sold out".
Web page change monitoring and discord telegram alerts
Check out our tutorials page for ideas and inspiration of how you can monitor for changes
NEW: We provide official, private and very affordable hosting of this image, use our proxies and support!

Example use cases

Know when ...
  • Government department updates (changes are often only on their websites)
  • Local government news (changes are often only on their websites)
  • New software releases, security advisories when you're not on their mailing list.
  • Festivals with changes
  • Realestate listing changes
  • Detect and compare changes in JSON data
  • and many many more

Get monitoring now! super simple, one command!
```bash docker run -d --restart always -p "127.0.0.1:5000:5000" -v datastore-volume:/datastore --name changedetection.io dgtlmoon/changedetection.io ```
Or use the docker-compose.yml https://github.com/dgtlmoon/changedetection.io/blob/master/docker-compose.yml
Now visit http://127.0.0.1:5000 , You should now be able to access the UI.
More information about JSON filters, CSS filters, notification configuration, upgrading, etc please visit the GitHub page https://github.com/dgtlmoon/changedetection.io/

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs changedetection
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/changedetection

Image won't pull

Test the pull directly on the host: docker pull dgtlmoon/changedetection.io:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64, arm/v7, arm/v8
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The always restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect changedetection --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

Change Detection runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Change Detection needs bundled into one download. This template pulls dgtlmoon/changedetection.io:latest, which Docker fetches once (about 371 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Change Detection's comes from Docker Hub, published by dgtlmoon.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 0.60. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, arm/v8, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Volumes

A volume is where Change Detection keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /datastore from /portainer/Files/AppData/Config/changedetection on the host

Restart policy

The restart policy here is always, so Docker brings Change Detection back up after a crash and again when the server reboots. Good for anything you want running around the clock. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so Change Detection sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container changedetection. That's what you'll spot in the containers list and use in commands like docker logs changedetection.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Open source license

Change Detection is open source, released under the Apache-2.0 license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Change Detection up. Add the template list to Portainer once, then deploying Change Detection is a click rather than a wall of config.