chore: update paths for secrets and properties

Author: lukepolo

discord-bot/index.md

@@ -19,16 +19,16 @@ First, you need to create a new application in the [Discord Developer Portal](ht
 
     ![Oauth URL](./discord-oauth.png)
 
-    * Update the Redirect URL to your `WEB_DOMAIN` URL, which can be found in `INSTALL_DIR/base/properties/api-config.env`.
-    * Update the `INSTALL_DIR/overlays/secrets/discord-secrets.env`, you need to update both the `DISCORD_CLIENT_ID` and `DISCORD_CLIENT_SECRET`.
+    * Update the Redirect URL to your `WEB_DOMAIN` URL, which can be found in `INSTALL_DIR/overlays/config/api-config.env`.
+    * Update the `INSTALL_DIR/overlays/local-secrets/discord-secrets.env`, you need to update both the `DISCORD_CLIENT_ID` and `DISCORD_CLIENT_SECRET`.
 
 4. Bot Tab 
 
     1. You will need to reset the bot token to get a new one.      
 
       ![Reset Token](./discord-reset-token.png)
 
-    In the file `INSTALL_DIR/overlays/secrets/discord-secrets.env`, you need to update the `DISCORD_BOT_TOKEN`.
+    In the file `INSTALL_DIR/overlays/local-secrets/discord-secrets.env`, you need to update the `DISCORD_BOT_TOKEN`.
 
     2. Disable Public Bot
 

install/cookie-domain.md

@@ -2,7 +2,7 @@
 
 The cookie domain is the domain that the cookies will be set to. This is used to secure the cookies and prevent cross-site scripting (XSS) attacks. By Default the cookie domain is set to your `WEB_DOMAIN` (e.g. `.5stack.gg`) environment variable.
 
-This can be changed by setting the `AUTH_COOKIE_DOMAIN` environment variable which you can set in the `<INSTALL_DIR>/base/properties/api-config.env` file.
+This can be changed by setting the `AUTH_COOKIE_DOMAIN` environment variable which you can set in the `<INSTALL_DIR>/overlays/config/api-config.env` file.
 
 ::: warning
 The cookie domain should have a `.` infront to allow the other subdomains to be used (e.g. `.api.5stack.gg`).

install/index.md

@@ -14,4 +14,4 @@ Please ensure you have met the [Requirements](/install/requirements) before you
 
 Inside the 5Stack-Panel directory, run the installation script `./install.sh`.
 
-After installing, you can make changes to the configuration files in the `base/properties` or `overlays/secrets` directories. If modified, you will need to update 5Stack. See the [Updating Guide](/install/updating) for instructions.
+After installing, you can make changes to the configuration files in the `overlays/config` or `overlays/local-secrets` directories. If modified, you will need to update 5Stack. See the [Updating Guide](/install/updating) for instructions.

install/nginx.md

@@ -1,3 +1,3 @@
 # Nginx Configuration
 
-If ports 80 and 443 are already in use on your system, you can modify the Nginx configuration by editing `<INSTALL_DIR>/base/properties/nginx-config.env`.
+If ports 80 and 443 are already in use on your system, you can modify the Nginx configuration by editing `<INSTALL_DIR>/overlays/config/nginx-config.env`.

s3/index.md

@@ -10,6 +10,6 @@ The S3 storage is primarily used for storing match demos and backups. When a mat
 
 The default configuration uses MinIO, but you can override this by modifying the following files:
 
-1. Update the S3 `S3_ENDPOINT`, `S3_USE_SSL`, and `S3_PORT` configuration in `<INSTALL_DIR>/base/properties/s3-config.env`:
+1. Update the S3 `S3_ENDPOINT`, `S3_USE_SSL`, and `S3_PORT` configuration in `<INSTALL_DIR>/overlays/config/s3-config.env`:
 
-2. Update the S3 credentials in `<INSTALL_DIR>/overlays/secrets/s3-secrets.env` with your provider's access key and secret key.
+2. Update the S3 credentials in `<INSTALL_DIR>/overlays/local-secrets/s3-secrets.env` with your provider's access key and secret key.