[Feature]: Passing secrets via JVM Properties

[ILikePlayingGames]

🚀 Description

Could you please consider making the bot check for secrets (bot token, webhooks) in JVM properties on startup so they can be loaded from an env.properties file for example (launch logic would handle the property loading, not sdlink)? This would be an alternative to storing them in the config file.

Context: Support thread

💡 Use Case

Example use cases

• Server configuration versioned in git and deployed using CI/CD
  • Bad practice to store secrets in version control, so preferable to keep them in an environment file on the server
• A server network where multiple servers are deployed with the same configuration, but each require a unique set of secrets (Suggested by Kaleidio)

[hypherionmc]

(Just adding here that while this is considered, a current SDL config file can be submitted to version control, without removing secrets. Since v3 all secrets in the config is encrypted with a key unique to each server. As long as you don't commit that key to GitHub as well, you should be fine).

Also worth noting that SDL4 will be handling webhook configurations and urls automatically, so they will no longer be stored in the config. The only "secret" will be your bot token