From 9f2cf28a762ac5e49b84b7d9b38bce496862e34b Mon Sep 17 00:00:00 2001 From: Rakovskij Stanislav Date: Tue, 30 Apr 2024 23:53:27 +0300 Subject: [PATCH] Making docker usage with localhost and external ip more clear (#3836) Co-authored-by: Frank Elsinga --- README.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 0459692ae..0cb8fe3f1 100644 --- a/README.md +++ b/README.md @@ -43,11 +43,18 @@ It is a temporary live demo, all data will be deleted after 10 minutes. Sponsore docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1 ``` -Uptime Kuma is now running on http://localhost:3001 +Uptime Kuma is now running on . > [!WARNING] > File Systems like **NFS** (Network File System) are **NOT** supported. Please map to a local directory or volume. +> [!NOTE] +> If you want to limit exppoure to localhost (without exposing port for other users or to use a [reverse proxyx](https://github.com/louislam/uptime-kuma/wiki/Reverse-Proxy)), you can expose the port like this: +> +> ```bash +> docker run -d --restart=always -p 127.0.0.1:3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1 +> ``` + ### 💪🏻 Non-Docker Requirements: