as-loadingscreen

Discord Feed Bridge (Express + Discord Bot)

This service exposes read-only JSON endpoints that your FiveM loading screen can poll to display Discord-style feeds like News / Devlog / Events. Purchase required: You need the loading screen resource. Get it here: https://alva-scripts.com/scripts/7243673

Security (Read This)

Golden rule: Only give the bot access to channels you want to display publicly. Never allow the bot to view staff/private/ticket/log channels.

If the bot can see a channel, this service can read it. You do have an allowlist layer in .env, but you should still follow this rule 100%. {% endhint %}

---

Requirements

• VPS or machine that can run Node.js

• Node.js LTS (recommended)

• Discord bot token

• (Recommended) Domain + Nginx + HTTPS

---

Discord Bot Setup

1) Create a bot

Create a new application + bot in the Discord Developer Portal: https://discord.com/developers/applications?new_application=true

2) Invite the bot to your server

• The bot does not need special permissions

• Just ensure it can View Channel + Read Message History for the channels you want to expose

Invite Bot Screenshot

3) Enable Message Content Intent

Enable Message Content Intent so message text is available reliably:

Enable Message Content Intent Screenshot

4) Copy your bot token

Copy the token (marked as (1) in the screenshot above). Keep it secret.

5) Create .env

Copy .env.example → rename to .env and place it next to .env.example.

---

Install (Linux / VPS)

1. Clone:

git clone <YOUR_REPO_URL>
cd discord-feed

1. Make script executable:

chmod +x install.sh

1. Run:

sudo ./install.sh

The script will ask for:

• Discord bot token

• Guild ID (recommended)

• Allowed channel IDs (comma separated)

• Domain (optional — leave empty to skip Nginx/HTTPS)

1) Install Node.js (Debian/Ubuntu)

sudo apt update
sudo apt install -y curl ca-certificates
curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo -E bash -
sudo apt install -y nodejs

2) Install dependencies

cd discord-feed
npm install

3) Create .env

Create a file named .env in the project folder:

DISCORD_TOKEN=PUT_YOUR_BOT_TOKEN_HERE
PORT=3001
CACHE_TTL_MS=8000

# CORS (set your domain in production instead of "*")
ALLOWED_ORIGINS=*

# Security: restrict to your Discord server
GUILD_ID=1342863880879345716

# Security: only these channels can be queried
ALLOWED_CHANNEL_IDS=1464942736070148321,1464942754147598473,1464942768223944725

# Rate limiting (per IP)
RATE_LIMIT_MAX=5
RATE_LIMIT_WINDOW_MS=60000

Notes

• ALLOWED_CHANNEL_IDS should only include channels you want public

• GUILD_ID ensures only channels from your server can be read

• ALLOWED_ORIGINS should be your domain in production (not *)

4) Run

npm start

Test

curl http://127.0.0.1:3001/health
curl "http://127.0.0.1:3001/feed/1464942736070148321?limit=10"

---

Domain Setup (Optional)

If you want a clean URL like feed.yourdomain.com:

1. In your DNS provider (Cloudflare, Namecheap, etc.) create an A record:

• Host: feed (or @)

• Type: A

• Value: YOUR_VPS_PUBLIC_IP

• TTL: Auto

Then configure Nginx + HTTPS below (or let the install script do it).

---

Production (Nginx + HTTPS)

systemd service

sudo nano /etc/systemd/system/discord-feed.service

[Unit]
Description=Discord Feed Bridge
After=network.target

[Service]
Type=simple
User=root
WorkingDirectory=/root/discord-feed
ExecStart=/usr/bin/npm start
Restart=always
RestartSec=3
Environment=NODE_ENV=production

[Install]
WantedBy=multi-user.target

sudo systemctl daemon-reload
sudo systemctl enable discord-feed.service
sudo systemctl start discord-feed.service
sudo systemctl status discord-feed.service --no-pager

Nginx reverse proxy

sudo apt update
sudo apt install -y nginx
sudo nano /etc/nginx/sites-available/discord-feed

server {
    listen 80;
    server_name YOURDOMAIN.com;

    location / {
        proxy_pass http://127.0.0.1:3001;
        proxy_http_version 1.1;

        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

sudo ln -s /etc/nginx/sites-available/discord-feed /etc/nginx/sites-enabled/discord-feed
sudo nginx -t
sudo systemctl reload nginx

HTTPS (Let’s Encrypt)

sudo apt install -y certbot python3-certbot-nginx
sudo certbot --nginx -d YOURDOMAIN.com

---

Use In Loading Screen Config

feeds: [
  {
    id: "news",
    type: "discord",
    title: "News",
    subtitle: "Latest announcements",
    enabled: true,
    discord: {
      endpoint: "https://YOURDOMAIN.com/feed/1464942736070148321",
      pollMs: 15000,
      limit: 25,
      showAvatars: true,
    },
  },
]

layout: {
  tabs: [
    { id: "feed:news", label: "News" },
  ]
}

---

Troubleshooting

Messages are empty / missing

• Enable Message Content Intent in the Discord Developer Portal

• Ensure the bot can View Channel + Read Message History

403 — Channel not allowed

• Add the channel ID to ALLOWED_CHANNEL_IDS in .env

403 — Channel not in allowed guild

• Set the correct GUILD_ID in .env