Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Making docker usage with localhost and external ip more clear #3836

Merged
merged 4 commits into from
Apr 30, 2024
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,14 @@ docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name upti

⚠️ Please use a **local volume** only. Other types such as NFS are not supported.

Uptime Kuma is now running on http://localhost:3001
Uptime Kuma is now running on http://<your_external_ip>:3001 (and http://127.0.0.1:3001 too).

If you want to run it at localhost (without exposing port for other users or to use with nginx), you can expose port like that:

```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
```
CommanderStorm marked this conversation as resolved.
Show resolved Hide resolved

rakovskij-stanislav marked this conversation as resolved.
Show resolved Hide resolved

### 💪🏻 Non-Docker

Expand Down