docs: add documentation for DISABLE_ENCRYPTION (#50)

* docs: add documentation for OVERRIDE_ENCRYPTION

* chore: rename OVERRIDE_ENCRYPTION to DISABLE_ENCRYPTION

* fix: DISABLE_ENCRYPTION callout list

Author: LeonTheDev-io

docs/self-hosting/configuration.md

@@ -24,6 +24,7 @@ The installation guides also explain where to find most of the environment varia
 	```bash title=".env"
 	DB_CONNECTION_URL="mysql://bots:VerySecurePassword123@localhost/tickets0"
 	DB_PROVIDER=mysql
+	DISABLE_ENCRYPTION=
 	DISCORD_SECRET=rUpDU2T8K4ZXie8kdpzYsMTLbUhvmBRd
 	DISCORD_TOKEN=ODcwOTg1TY0NjI0NODI2Mzc0.DNg0e0.UYVof7V1v0kRA0HHtGwXKA3URxwANAZhQiA
 	ENCRYPTION_KEY=445940dbed49eff55df56dd646fa1cb4b686df4cb9ac004a
@@ -68,6 +69,20 @@ The type of database the bot will use; one of:
 - `#!yaml postgresql`
 - `#!yaml sqlite`
 
+### `DISABLE_ENCRYPTION`
+
+<small>:octicons-question-16: Optional</small>
+
+When set to `#!yaml true` (must be lowercase), encryption/decryption calls will return the input data as-is, disabling data encryption for the instance.
+
+!!! danger
+	**Important!**
+	Changing this option after initial setup requires a full database reset or migration.
+	The migration process needs to **encrypt or decrypt all relevant data fields accordingly** to avoid errors.
+
+    - If you enable it after it was previously disabled or unset, the bot won't be able to decrypt some existing encrypted data properly.
+    - If you disable it after it was previously enabled, the bot will error when trying to decrypt existing unencrypted data.
+
 ### `DISCORD_SECRET`
 
 Your Discord application's secret key, used for OAuth2.

docs/self-hosting/installation/docker.md

@@ -103,6 +103,7 @@ services:
     # https://discordtickets.app/self-hosting/configuration/#environment-variables
     environment:
       DB_CONNECTION_URL: mysql://tickets:insecure@mysql/tickets # (4)!
+      DISABLE_ENCRYPTION: null
       DISCORD_SECRET: # (5)!
       DISCORD_TOKEN: # (6)!
       ENCRYPTION_KEY: # (7)!