BotMeriendo reads its configuration from environment variables loaded viaDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/Melendo/BotMeriendo/llms.txt
Use this file to discover all available pages before exploring further.
python-dotenv from a .env file in the project root. Copy .env.example to .env and fill in the values before starting the bot — the application calls validate_config() at boot and will refuse to start if any required variable is absent.
.env.example
The repository ships a template you can use as a starting point:.env and replace the placeholder values with your real credentials:
Variable Reference
The Discord bot token obtained from the Discord Developer Portal.BotMeriendo passes this value directly to Never share or commit this value — it grants full control over the bot account.
bot.start(TOKEN) in src/main.py. If this variable is missing or empty, validate_config() in src/config.py raises a ValueError and the process exits before the bot ever connects:The command prefix character(s) that BotMeriendo listens for before each command name (e.g. You can set this to any string. Common choices include
!play, >>play, ?play).If the variable is not set or is empty, the prefix falls back to !:!, >>, ?, or $.Loading order
Variables defined in
.env are loaded by python-dotenv via load_dotenv() at import time in src/config.py. If the same variable is already present in the system environment (e.g. set in a Docker Compose environment block or exported in your shell), the system value takes precedence and the .env value is ignored. This lets you override settings per-environment without editing the file.Security
Example: custom prefix
The following.env configures BotMeriendo to use >> as its command prefix:
>>play, >>skip, >>queue, and so on.