jjdevelopment/uptime-kuma-ping-service repository overview

⁠Uptime Kuma Ping Service

This Docker is to get an ping from an Uptime Kuma⁠ service. Here you will find a little introduction on how to use it.

The whole thing is brought to run in a Docker container. For this, a few variables from the Dockerfile are needed, if they are not stored, then they have a default value stored. You can find the variables here.

If the ENABLE_SSL is set to true, then the certificate names must be stored. These must be stored in the volume mapping. Below are the instructions for SSL.

⁠Launch Docker Container

To start the container properly, here is a small template. A volume mapping is only required if the application is to be operated with SSL.

⁠With SSL

docker run -d --restart always --name uptime-kuma-ping-service -e ENABLE_SSL='true' -e CERTIFICATE_CRT_NAME='...fullchain.pem' -e CERTIFICATE_KEY_NAME='...key.pem' -v /var/lib/certificates:/go/src/app/files/certificates -p 443:443 jjdevelopment/uptime-kuma-ping-service:latest

⁠Without SSL

docker run -d --restart always --name uptime-kuma-ping-service -p 80:443 jjdevelopment/uptime-kuma-ping-service:latest

Now the container can be started, so that your Uptime Kuma can connect to your server and check the service directly. So you know directly if Docker is still running on the server.

Click here⁠ to go directly to the Docker HUB.

⁠Contribute

If you want to help with development, or have found a bug, open a new issue⁠.