← Directory

Red-Discordbot

Red-Discordbot is a self-hosted, multi-arch Docker image for Red-DiscordBot that gives homelab users an easy, non-root way to run and keep a customizable…

  • Automation
  • Communication
  • Tools & Utilities
Red-Discordbot is a self-hosted, multi-arch Docker image for Red-DiscordBot that gives homelab users an easy, non-root way to run and keep a customizable Discord bot updated.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

57/100 Fair

Maintained
71last commit 43 days ago
Popular
51354 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 15 days ago

GitHub stars
354
Open issues
0
Last commit
2026-09-02
License
GPL-3.0
Activity
stale

Checked 8 days ago - source: GitHub (PhasecoreX/docker-red-discordbot)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Expose port 1880 and keep /data Run the container with port 1880 mapped and a volume attached to /data. This keeps your saved workflows and settings safe, and port 1880 is the web editor you open in a browser. source
  • Add credentialSecret to settings Add a value for credentialSecret in /data/settings.js. This is a password-like key Node-RED uses to encrypt saved logins and tokens; without it, losing the temporary system key can make those credentials unrecoverable. source
  • Match data folder ownership to 1000 If you use your own folder for /data, set its owner and group IDs to 1000:1000 (usually your normal user). If the ownership is wrong, Node-RED can't read or save your flows and settings. source
  • First install Create a Discord bot account and provide its token before starting the container. source

Fetched 7 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where should I store Red-DiscordBot data in the container?

Mount a host folder or named volume to /data to persist the bot's data. The quick start command uses a local folder for persistence.

Do I need to keep the token and prefix environment variables after the first run?

No, once the bot has run you can remove the TOKEN and PREFIX variables because they are saved to the bot's config.

Why does the first start take longer than later restarts?

With a new /data mount, the container may take longer on first start while the Red-DiscordBot software is updated. Subsequent restarts should be faster.

Which user does the bot run as, and who owns files it creates?

Use PUID and optionally PGID to choose the user and group; all files Red-DiscordBot creates are owned by that user on the host. The defaults are PUID 1000 and PGID set to the PUID value.

Can I configure more than one command prefix?

Yes, set PREFIX for the first prefix and use PREFIX2, PREFIX3, PREFIX4, and PREFIX5 for additional prefixes.

How does the container stay up to date?

The bot updates itself to the latest PyPi release of Red-DiscordBot on every restart.

Answers sourced from github.com

Community

Collected 11 days ago - public community threads