Skip to content

Latest commit

 

History

History
24 lines (14 loc) · 2.66 KB

CONFIG.md

File metadata and controls

24 lines (14 loc) · 2.66 KB
Raw

Configuration

This document defines the dev.env variables used to configure the Discord bot. To get started, copy dev.env.template file to dev.env.

These are the default settings to connect to Lavalink v4. If you're willing to use different host, port, and password, please make a copy of wavelink/application.yml.template to wavelink/application.yml and change the settings accordingly. Please configure Lavalink's yml file if you want to use proxy, changing the server port, password and so on.

Enabling plugins other than YouTube is not recommended as its optimized for YouTube playback.

  • ENV_LAVALINK_HOST - Host where Lavalink server is running (defaults to local server: 127.0.0.1)
  • ENV_LAVALINK_PORT - Lavalink port number (defaults to 2222)
  • ENV_LAVALINK_PASS - Lavalink password (change this if connecting remotely) - (defaults to "youshallnotpass")

Please do not use this module in production unless you're serving it yourself or other remote content than YouTube.

  • GOOGLE_AI_TOKEN - Set the Gemini API token, get one at Google AI Studio. If left blank, generative features will be disabled.

  • SYSTEM_USER_ID - If you're hosting a bot, please set your Discord user ID to adminisrate the bot even if you're not the administrator of the server. With great power coems great responsibility! This is used for commands like $admin_execute ($eval as alias) to do tasks like $eval git pull --rebase or $eval free -h

  • CHAT_HISTORY_DB - Path to the SQLite database file to store chat history. Defaults to chat_history.db in the current directory if not set.

  • TEMP_DIR - Path to store temporary uploaded/downloaded attachments for multimodal use. Defaults to temp/ in the cuurent directory if not set. Files are always deleted on every execution regardless if its successful or not, or when the bot is restared.

  • SHARED_CHAT_HISTORY - Determines whether to share the chat history to all members inside the guild. Accepts case insensitive boolean values. We recommend setting this to false as the bot does not have admin controls to manage chat history guild wide and conversations are treated as single dialogue. Setting to false makes it as if interacting the bot in DMs having their own history regardless of the setting. Keep in mind that this does not immediately delete per-guild chat history when set to false. Use SQLite database browser to manually manage history, refer to HistoryManagement class for more information.