update config docs

Author: topi314

docs/configuration/config/environment-variables.md

@@ -2,9 +2,12 @@
 description: How to configure Lavalink
 ---
 
-# Configuration
+# Environment Variables
 
-The server configuration is done in `application.yml`. You can find an example below.
+You can also use environment variables to configure the server. The environment variables are named the same as the keys in the `application.yml` file, but in uppercase and with `.` replaced with `_`. For example, `server.port` becomes `SERVER_PORT`.
+For arrays, the index is appended to the key, starting at 0. For example, `LAVALINK_PLUGINS_0_DEPENDENCY` refers to the `dependency` key of the first plugin.
+
+You can also use a combination of both. Environment variables take precedence over the `application.yml` file.
 
 ## Example application.yml
 
@@ -17,14 +20,8 @@ The server configuration is done in `application.yml`. You can find an example b
 
 </details>
 
-Alternatively, you can also use environment variables to configure the server. The environment variables are named the same as the keys in the `application.yml` file, but in uppercase and with `.` replaced with `_`. For example, `server.port` becomes `SERVER_PORT`.
-For arrays, the index is appended to the key, starting at 0. For example, `LAVALINK_PLUGINS_0_DEPENDENCY` refers to the `dependency` key of the first plugin.
-
 ## Example environment variables
 
-<details markdown="1">
-<summary>environment variables</summary>
-
 ```env title="enviroment variables"
 SERVER_PORT
 SERVER_ADDRESS
@@ -88,6 +85,10 @@ LAVALINK_SERVER_HTTP_CONFIG_PROXY_PORT
 LAVALINK_SERVER_HTTP_CONFIG_PROXY_USER
 LAVALINK_SERVER_HTTP_CONFIG_PROXY_PASSWORD
 
+LAVALINK_SERVER_TIMEOUTS_CONNECT_TIMEOUT_MS
+LAVALINK_SERVER_TIMEOUTS_CONNECTION_REQUEST_TIMEOUT_MS
+LAVALINK_SERVER_TIMEOUTS_SOCKET_TIMEOUT_MS
+
 METRICS_PROMETHEUS_ENABLED
 METRICS_PROMETHEUS_ENDPOINT
 
@@ -110,7 +111,3 @@ LOGGING_REQUEST_MAX_PAYLOAD_LENGTH
 LOGGING_LOGBACK_ROLLINGPOLICY_MAX_FILE_SIZE
 LOGGING_LOGBACK_ROLLINGPOLICY_MAX_HISTORY
 ```
-
-</details>
-
-You can also use a combination of both. Environment variables take precedence over the `application.yml` file.

docs/configuration/config/config-file.md renamed to docs/configuration/config/file.md

@@ -6,7 +6,7 @@ description: How to configure Lavalink with the Config Server
 
 ## Example Lavalink application.yml
 
-To configure Lavalink to pull it's configuration from a [Lavalink Config Server](https://github.com/lavalink-devs/Lavalink-Config-Server) you need to put the following in your `application.yml` file:
+To configure Lavalink to pull its configuration from a [Lavalink Config Server](https://github.com/lavalink-devs/Lavalink-Config-Server) you need to put the following in your `application.yml` file:
 
 ```yaml title="application.yml"
 --8<-- "LavalinkServer/application.yml.cloud-example"
@@ -18,7 +18,8 @@ Alternatively, this can also be done via environment variables:
 <summary>Environment Variables</summary>
 
 ```bash
-SPRING_APPLICATION_NAME
+SPRING_CLOUD_CONFIG_ENABLED
+SPRING_CLOUD_CONFIG_NAME
 SPRING_CLOUD_CONFIG_PROFILE
 SPRING_CLOUD_CONFIG_LABEL
 SPRING_CLOUD_CONFIG_FAIL_FAST
@@ -34,9 +35,9 @@ SPRING_CONFIG_IMPORT
 
 To run the Lavalink Config Server, you can use the docker image located at [`ghcr.io/lavalink-devs/lavalink-config-server`](https://github.com/lavalink-devs/Lavalink-Config-Server/pkgs/container/lavalink-config-server)
 
-### Example docker-compose.yml
+### Example compose.yml
 
-```yaml
+```yaml title="compose.yml"
 services:
   lavalink-config-server:
     image: ghcr.io/lavalink-devs/lavalink-config-server:master
@@ -173,4 +174,4 @@ The config repository should have the following structure:
 
 The `application.yml` file is the default configuration file.
 The `application-{profile}.yml` file is the configuration file for the specified profile and overrides the config entries in the default configuration file.
-The profile name can be set in the [`application.yml`](#example-applicationyml) file of the Lavalink server.
+The profile name can be set in the [`application.yml`](file.md#example-applicationyml) file of the Lavalink server.

docs/configuration/config/config-server.md renamed to docs/configuration/config/server.md

@@ -15,9 +15,9 @@ Install [Docker](https://docs.docker.com/engine/install/) & [Docker Compose](htt
 | `Alpine`     | Smaller image size, based on Alpine          | 21           | 322   | 322   | `ghcr.io/lavalink-devs/lavalink:4-alpine`     |
 | `Distroless` | Even smaller image size, based on Distroless | 21           | 65534 | 65534 | `ghcr.io/lavalink-devs/lavalink:4-distroless` |
 
-Create a `docker-compose.yml` with the following content:
+Create a `compose.yml` with the following content:
 
-```yaml title="docker-compose.yml"
+```yaml title="compose.yml"
 services:
   lavalink:
     # pin the image version to Lavalink v4 and use the alpine variant for a smaller image size
@@ -52,7 +52,7 @@ networks:
     name: lavalink
 ```
 
-Create an `application.yml` file in the same directory as the `docker-compose.yml` file. ([Example here](index.md#example-applicationyml)) or use environment variables ([Example here](index.md#example-environment-variables))
+Create an `application.yml` file in the same directory as the `compose.yml` file. ([Example here](../configuration/config/file.md#example-applicationyml)) or use environment variables ([Example here](../configuration/config/environment-variables.md#example-environment-variables))
 
 Run `docker compose up -d`. See [Docker Compose Up](https://docs.docker.com/engine/reference/commandline/compose_up/)