From 738c86dcdfcccb0e20cfb96f4cc24c64813b7bda Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Tue, 29 Jul 2025 21:56:18 -0600 Subject: [PATCH] Update Servers/Containerization/Docker/Compose/Speedtest Tracker.md --- Servers/Containerization/Docker/Compose/Speedtest Tracker.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Servers/Containerization/Docker/Compose/Speedtest Tracker.md b/Servers/Containerization/Docker/Compose/Speedtest Tracker.md index b508f16..d3b991b 100644 --- a/Servers/Containerization/Docker/Compose/Speedtest Tracker.md +++ b/Servers/Containerization/Docker/Compose/Speedtest Tracker.md @@ -20,7 +20,7 @@ services: - APP_TIMEZONE=${TIMEZONE} - DISPLAY_TIMEZONE=${TIMEZONE} - SPEEDTEST_SCHEDULE=*/15 * * * * # (1) - - SPEEDTEST_SERVERS=5858 + - SPEEDTEST_SERVERS=5858 # (3) - APP_KEY=${BASE64_APPKEY} # (2) - DB_CONNECTION=pgsql - DB_HOST=db @@ -67,6 +67,8 @@ networks: 2. You can generate a secure appkey with the following command: `echo -n 'base64:'; openssl rand -base64 32;` > Copy this key including the `base64:` prefix and paste it as your APP_KEY environment variable value. +3. This restricts the speedtest target to a specific speedtest server. In this example, it is a Missoula, MT speedtest server. You can get these codes from the yellow Speedtest button menu in the WebUI and then come back and redeploy the stack with the number entered here. + ```yaml title=".env" DB_PASSWORD=SecurePassword DB_DATABASE=speedtest_tracker