elestio/uptime-kuma

https://img.shields.io/static/v1.svg?logo=***&color=f78A38&labelColor=083468&logoColor=ffffff&style=for-the-badge&label=***&message=community]([***] "Get instant assistance and engage in live discussions with both the community and team through our chat feature.") https://img.shields.io/static/v1.svg?logo=github&color=f78A38&labelColor=083468&logoColor=ffffff&style=for-the-badge&label=github&message=open%20source](https://github.com/elestio-examples "Access the source code for all our repositories by viewing them.") https://img.shields.io/static/v1.svg?color=f78A38&labelColor=083468&logoColor=ffffff&style=for-the-badge&label=elest.io&message=Blog](https://blog.elest.io "Latest news about elestio, open source software, and DevOps techniques.")

Uptime-Kuma, verified and packaged by Elestio

https://github.com/louislam/uptime-kuma is an open source monitoring tool. It enables you to monitor services over HTTP/S, TCP, DNS, and other protocols.

Deploy a https://elest.io/open-source/uptime-kuma on https://elest.io/ if you want a great solution that allows the creation of simple and easy-to-use monitoring dashboards to monitor the status of servers, applications, and services.

Why use Elestio images?

• Elestio stays in sync with updates from the original source and quickly releases new versions of this image through our automated processes.
• Elestio images provide timely access to the most recent bug fixes and features.
• Our team performs quality control checks to ensure the products we release meet our high standards.

Usage

Docker-compose

Here are some example snippets to help you get started creating a container.

version: '3.3'

services:
uptime-kuma:
    image: elestio/uptime-kuma:${SOFTWARE_VERSION_TAG}
    restart: always
    healthcheck:
    disable: true
    volumes:
    - ./data:/app/data
    ports:
    - '172.17.0.1:***:3001'

Environment variables

Access

You can access the Web UI at: http://your-domain:13001

Maintenance

Logging

The Elestio uptime-kuma Docker image sends the container logs to stdout. To view the logs, you can use the following command:

docker-compose logs -f

To stop the stack you can use the following command:

docker-compose down

Backup and Restore with Docker Compose

To make backup and restore operations easier, we are using folder volume mounts. You can simply stop your stack with docker-compose down, then backup all the files and subfolders in the folder near the docker-compose.yml file.

Creating a ZIP Archive For example, if you want to create a ZIP archive, navigate to the folder where you have your docker-compose.yml file and use this command:

zip -r myarchive.zip .

Restoring from ZIP Archive To restore from a ZIP archive, unzip the archive into the original folder using the following command:

unzip myarchive.zip -d /path/to/original/folder

Starting Your Stack Once your backup is complete, you can start your stack again with the following command:

docker-compose up -d

That's it! With these simple steps, you can easily backup and restore your data volumes using Docker Compose.

Links

• https://github.com/louislam/uptime-kuma.git

• uptime-kuma documentation