https://github.com/torantulino/discord-bot-proxy
https://github.com/torantulino/discord-bot-proxy
Last synced: about 1 month ago
JSON representation
- Host: GitHub
- URL: https://github.com/torantulino/discord-bot-proxy
- Owner: Torantulino
- License: mit
- Created: 2025-04-21T13:02:13.000Z (about 2 months ago)
- Default Branch: master
- Last Pushed: 2025-04-21T14:59:19.000Z (about 2 months ago)
- Last Synced: 2025-04-23T15:17:32.110Z (about 1 month ago)
- Language: Python
- Size: 43 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# ! WARNING | THIS REPO IS ENTIRELY "VIBE CODED" BY AN AI AND SHOULD BE TREATED AS INSECURE | NEVER RUN OR DEPLOY CODE FROM THIS REPO WITHOUT FIRST REVIEWING IT !
# Discord ↔ Platform **Relay Bot**
A one‑file, open‑source proxy that forwards every new Discord message to **your** webhook and lets your platform post messages back into Discord via a simple, HMAC‑secured REST endpoint.
---
## ✨ Features
* **Listen**: Subscribes to `MESSAGE_CREATE`, filters out bot traffic, and `POST`s a clean JSON payload to `FORWARD_WEBHOOK`.
* **Talk back**: `/send` endpoint accepts `{channel_id, content}` and posts into that channel.
* **Secure by default**: Shared‑secret HMAC (`X‑Relay‑Signature`) + 5‑minute replay window.
* **Zero ops**: Deploy to [Railway](https://railway.app) in one click, free tier friendly (<100 MB RAM).
---
## 🚀 One‑click deploy (Railway)
[](https://railway.com/template/9bTw8E?referralCode=R5sBUf)
1. Click the button above.
2. Add these **environment variables** when prompted:
| Key | Example | Notes |
|-----|---------|-------|
| `DISCORD_TOKEN` | `MTEx…t.XYZ` | From *Bot → Reset Token* in the Discord Developer Portal. |
| `FORWARD_WEBHOOK` | `https://platform.example.com/webhook/abc` | Your platform’s incoming webhook URL. |
| `RELAY_SHARED_SECRET` | `6f7f3d…` | 32‑byte random hex; generate with `openssl rand -hex 32`. |
3. Hit **Deploy**. Railway builds, runs, and assigns a public HTTPS URL (e.g. `https://relay-production.up.railway.app`).
4. Copy that URL; your platform will use `https://…/send` for outbound messages.
> **Privileged intent:** In the Discord Developer Portal, toggle **Message Content Intent** (Bot → Privileged Gateway Intents) or the bot cannot read message bodies.
---
## 🖥️ Local development
~~~bash
git clone https://github.com/Torantulino/Discord-Bot-Proxy
cd discord-relay-bot
python -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
cp .env.example .env # edit the three vars
python relay_bot.py # FastAPI on :8000, bot logs to stdout
~~~
### Signing helper (Python)
~~~python
import hmac, hashlib, time, requests, os, json
SECRET = os.getenv("RELAY_SHARED_SECRET")
body = json.dumps({"channel_id": 1234567890, "content": "hello world"}).encode()
ts = str(int(time.time()))
sig = "sha256=" + hmac.new(SECRET.encode(), ts.encode()+b"."+body, hashlib.sha256).hexdigest()
headers = {
"X-Relay-Timestamp": ts,
"X-Relay-Signature": sig,
"Content-Type": "application/json",
}
requests.post("https://YOUR-RAILWAY-URL/send", headers=headers, data=body)
~~~
---
## 📂 Repository layout
```
.
├── relay_bot.py # the proxy bot (see inline docstring)
├── requirements.txt # Python deps pinned loosely
├── railway.json # Railway build + run config
├── .gitignore # excludes virtualenvs, IDE junk, .env
└── README.md # you are here
```
### requirements.txt
~~~text
discord.py>=2.3.2
fastapi>=0.110.0
uvicorn[standard]>=0.29.0
aiohttp>=3.9.3
python-dotenv>=1.0.1
~~~
### railway.json
~~~json
{
"build": {
"builder": "NIXPACKS"
},
"deploy": {
"startCommand": "python relay_bot.py",
"healthcheckPath": "/"
}
}
~~~
---
## 🔒 Security notes
* All traffic must be HTTPS (Railway handles TLS).
* HMAC secret rotates just like any API key. Maintain two keys during cut‑over:
1. Add `RELAY_SHARED_SECRET_OLD`, accept either digest.
2. Update platform, wait, then remove the old variable.
* Discord rate limits: 50 messages/second per bot; if you approach this, add an internal queue and exponential back‑off.
---
## 🔑 How to get your `DISCORD_TOKEN`
1. **Open or create your application**
• Go to → **New Application** (or click an existing one).
2. **Add the bot user (if you don’t see a token yet)**
• Sidebar → **Bot**.
• If you see a “Build‑A‑Bot” panel with an **Add Bot** button, click it → **Yes, do it!**
• Once the bot exists you’ll land on the Bot settings page.
3. **Generate & copy the token**
• In the **Token** row click **New Token** (older UI: **Reset Token**).
• Confirm, then click **Copy**.
• **Paste it immediately** into `DISCORD_TOKEN` in Railway or your local `.env`. You won’t see it again unless you regenerate.
4. **Enable Message‑Content Intent**
• Same page, scroll to **Privileged Gateway Intents**.
• Toggle **Message Content Intent** → it turns purple.
• Click **Save Changes** at the bottom.
5. **Invite the bot to your server**
• Sidebar → **OAuth2 → URL Generator**.
• Scopes: check **bot**.
• Bot Permissions: check **Read Messages/View Channels** and **Send Messages**.
• Copy the generated link, open it, pick your server, **Authorize**.
> 🛡️ Treat the token like a production‑database password. Never commit it to Git, paste in screenshots, or send in chat.
---
## 🛠️ Discord bot setup recap
1. Create an **Application** → **Bot** → *Add Bot*.
2. Copy the token into `DISCORD_TOKEN` (keep it secret!).
3. Under *Privileged Gateway Intents* tick **Message Content Intent**.
4. *OAuth2 → URL Generator*: select scope `bot`, permissions `Read Messages/View Channels` + `Send Messages`.
5. Paste the invite URL into a browser, pick your server.
---
## 📜 License
MIT — see `LICENSE` for details. Commercial use welcome; attribution appreciated.