Further documentation updates

README-UPDATED.md

@@ -5,11 +5,11 @@ The aim of this project is to be entirely compatible with Upstash, and work with
 
 Use cases for SRH:
 - For usage in your CI pipelines, creating Upstash databases is tedious, or you have lots of parallel runs.
-    - See Using in GitHub Actions on how to quickly get SRH setup for this context.
+    - See [Using in GitHub Actions](#in-github-actions) on how to quickly get SRH setup for this context.
 - For usage inside of Kubernetes, or any network whereby the Redis server is not exposed to the internet.
-    - See Using in Docker Compose for the various setup options directly using the Docker Container.
+    - See [Using in Docker Compose](#via-docker-compose) for the various setup options directly using the Docker Container.
 - For local development environments, where you have a local Redis server running, or require offline access.
-    - See Using the Docker Command, or Using Docker Compose.
+    - See [Using the Docker Command](#via-docker-command), or [Using Docker Compose](#via-docker-compose).
 
 ## Differences between Upstash and Redis to note
 SRH tests are ran nightly against the `@upstash/redis` JavaScript package. However, there are some minor differences between Upstash's implementation of Redis and the official Redis code.
@@ -17,7 +17,7 @@ SRH tests are ran nightly against the `@upstash/redis` JavaScript package. Howev
 - The `UNLINK` command will not throw an error when 0 keys are given to it. In Redis, and as such SRH, an error will be thrown.
 - In the `ZRANGE` command, in Upstash you are not required to provide `BYSCORE` or `BYLEX` in order to use the `LIMIT` argument. With Redis/SRH, this will throw an error if not provided.
 - The Upstash implementation of `RedisJSON` contains a number of subtle differences in what is returned in responses. For this reason, **it is not advisable to use SRH with Redis Stack if you are testing your Upstash implementation that uses JSON commands**. If you don't use any JSON commands, then all is good :)
-- **SRH does not implement commands via paths, or accepting the token via a query param**. Only the body method is implemented, which the `@upstash/redis` SDK implements.
+- **SRH does not implement commands via paths, or accepting the token via a query param**. Only the body method is implemented, which the `@upstash/redis` SDK uses.
 
 ### Similarities to note:
 
@@ -71,7 +71,7 @@ services:
 
 ## In GitHub Actions
 
-SRH works nicely in GitHub actions because you can run it as a container in a job's services. Simply start a Redis server, and then
+SRH works nicely in GitHub Actions because you can run it as a container in a job's services. Simply start a Redis server, and then
 SRH alongside it. You don't need to worry about a race condition of the Redis instance not being ready, because SRH doesn't create a Redis connection until the first command comes in.
 
 ```yml
@@ -113,6 +113,33 @@ jobs:
 
 # Configuration Options
 
+SRH works with multiple Redis servers, and can pool however many connections you wish it to. It will shut down un-used pools after 15 minutes of inactivity. Upon the next command, it will re-build the pool.
+
 ## Connecting to multiple Redis servers at the same time
 
-## Environment Variables
+The examples above use environment variables in order to tell SRH which Redis server to connect to. However, you can also use a configuration JSON file, which lets you create as many connections as you wish. The token provided in each request will decide which pool is used.
+
+Create a JSON file, in this example called `tokens.json`:
+```json
+{
+    "example_token": {
+        "srh_id": "some_unique_identifier",
+        "connection_string": "redis://localhost:6379",
+        "max_connections": 3
+    }
+}
+```
+You can provide as many entries to the base object as you wish, and configure the number of max connections per pool. The `srh_id` is used internally to keep track of instances. It can be anything you want.
+
+Once you have created this, mount it to the docker container to the `/app/srh-config/tokens.json` file. Here is an example docker command:
+
+`docker run -it -d -p 8079:80 --name srh --mount type=bind,source=$(pwd)/tokens.json,target=/app/srh-config/tokens.json hiett/serverless-redis-http:latest`
+
+## Environment Variables
+
+| Name | Default Value | Notes |
+| ---- | ------------- | ----- |
+| SRH_MODE | `file` | Can be `env` or `file`. If `file`, see [Connecting to multiple Redis servers](#connecting-to-multiple-redis-servers-at-the-same-time). If set to `env`, you are required to provide the following environment variables: |
+| SRH_TOKEN | `<required if SRH_MODE = env>` | Set the token that the Rest API will require |
+| SRH_CONNECTION_STRING | `<required if SRH_MODE = env>` | Sets the connection string to the Redis server. |
+| SRH_MAX_CONNECTIONS | `3` | Only used if `SRH_MODE=env`.