From f3bfaefe23cd46cb9b925781540afe60045076f0 Mon Sep 17 00:00:00 2001 From: JP Meijers Date: Mon, 27 Feb 2017 12:33:24 +0100 Subject: [PATCH] Update README.md Clickable configuration link --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 654fac8..feac590 100644 --- a/README.md +++ b/README.md @@ -27,7 +27,7 @@ Two gateway boards are supported, but need to be used with a Raspberry Pi: Click the "Environment Variables" section at the left side of the screen. This will allow you to configure environment parameters for this and only this device, and which will be appropriately inserted into this device's "local_conf.json" with lowercase tuple names derived from the appropriate uppercase environment names beginning with "GW_". For example, for an IMST gateway with no GPS, the MINIMUM environment variables that you should configure at this screen should look something like this: -#### DEVICE ENVIRONMENT VARIABLES +DEVICE ENVIRONMENT VARIABLES Name | Value ------------------|-------------------------- @@ -38,7 +38,7 @@ GW_KEY | The gateway KEY from the TTN console On the other hand, for the LinkLabs gateway, which has a built-in GPS, you only need: -#### DEVICE ENVIRONMENT VARIABLES +DEVICE ENVIRONMENT VARIABLES Name | Value ------------------|-------------------------- @@ -48,7 +48,7 @@ GW_ID | The gateway ID from the TTN console GW_KEY | The gateway KEY from the TTN console GW_GPS | true -For a more complete list of possible environment variables, see CONFIGURATION.md. +For a more complete list of possible environment variables, see [CONFIGURATION](CONFIGURATION.md). ### SPECIAL Note for using the LinkLabs gateway on a Raspberry Pi 3 @@ -58,7 +58,7 @@ Click <- to go back to the Device List, and note that on the left there is an op Add a New config variable as follows: -#### APPLICATION CONFIG VARIABLES +APPLICATION CONFIG VARIABLES Name | Value ------------------------------|--------------------------