Skip to main content
You can run pwr-bot manually using pre-compiled binaries available for Linux, macOS, and Windows.

​
Prerequisites

1

Download the Binary

Download the latest binary for your platform from the GitHub Releases page.
Download pwr-bot-linux-x64 (or the appropriate architecture)
2

Download Configuration File

Download the .env-example file from the repository.Save it in the same directory as the binary and rename it to .env.
3

Configure Environment Variables

Edit the .env file with your text editor and configure the required variables.At minimum, you must set:
  • DISCORD_TOKEN - Your Discord bot token
  • ADMIN_ID - Your Discord user ID
See the Configuration guide for all available options.
4

Make Binary Executable (Linux/macOS)

This step is only required on Linux and macOS systems.
Open a terminal in the directory containing the binary and run:
chmod +x pwr-bot
Replace pwr-bot with the actual filename you downloaded.
5

Run the Bot

./pwr-bot
To run in the background:
nohup ./pwr-bot > output.log 2>&1 &
The bot should start and connect to Discord. Check the console output or logs directory for startup messages.

​
Directory Structure

By default, pwr-bot creates the following directories: 
.
├── pwr-bot          # Binary executable
├── .env             # Configuration file
├── data/            # Database and data files (auto-created)
│   └── data.db     # SQLite database
└── logs/            # Log files (auto-created)
You can customize the paths for data and logs directories using the DATA_PATH and LOGS_PATH environment variables.

​
Managing the Bot

# Press Ctrl+C in the terminal where the bot is running
# Or if running in background, find and kill the process:
pkill pwr-bot

​
Troubleshooting

Make sure you’ve made the binary executable:
chmod +x pwr-bot
Ensure only one instance of pwr-bot is running at a time. SQLite does not support multiple concurrent write connections.
Verify your DISCORD_TOKEN is correct in the .env file and that the bot has been invited to your server.

​
Next Steps

After the bot is running:
  1. Check the logs to ensure the bot started successfully
  2. See the command registration steps in the Quick Start guide
  3. Start using the bot’s features

Build docs developers (and LLMs) love

Get started for freeTalk to us