Skip to content

PariahBot 1.1.0

Choose a tag to compare

View all tags
@CosmicCubicle CosmicCubicle released this 12 Oct 12:06
Immutable release. Only release title and notes can be modified.
v1.1.0
a9a85e5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

PariahBot now ships as a container image for amd64 and arm64, with a guided setup script. This release also adds per-server feature switches and hosting guides for AWS and Azure.

📖 Documentation: setup, configuration, per-server walkthroughs and troubleshooting.

Container image

ghcr.io/cosmiccubicle/pariahbot:1.1.0
Tag Follows
1.1.0 This release, and never changes
1.1 The newest 1.1.x release
latest Every change merged to main
sha-<commit> One specific build

What's new

Run it in a container

  • deploy/container-setup.sh installs Docker if it's missing, asks for your token, IDs and dashboard settings, and starts the bot with Docker Compose.
  • An optional job updates the container when a newer image appears.
  • The dashboard works exactly as before: on the host's own address, through an SSH or Cloudflare Tunnel.
  • Already running the bot under systemd on the same machine? The script offers to retire that install and bring its database into the container.

Hosting on AWS and Azure

  • Step-by-step guides for setting up a small Ubuntu VM on EC2 or Azure, for either install method.
  • They explain why a VM rather than Fargate or Container Apps: the bot's SQLite database needs a local disk, and exactly one copy may run.

Per-server feature switches

  • Admins can switch any feature set off for their server, and back on, with /setup feature or from the dashboard.
  • Settings are kept, and anything already running finishes.
  • /help marks what's off and how to turn it back on.

Fixes

  • sudo ./deploy/setup.sh works on a fresh clone. The script wasn't marked executable in the repository, so 1.0.0's install instructions failed with "command not found".
  • Rerunning setup.sh no longer stops partway when its git sync job is the only cron job.
  • Turning the sync job off now removes its cron entry too.
  • setup.sh stops with a clear message on hosts without apt-get, rather than failing partway.
  • Auto-delete no longer logs a deprecation warning on every startup.

Install

In a container, on any Linux host with Docker (or Ubuntu, where the script can install Docker):

git clone --branch v1.1.0 https://github.com/CosmicCubicle/PariahBot.git
cd PariahBot
sudo ./deploy/container-setup.sh

See Container Installation. The setup follows latest. To stay on this release series instead, put PARIAHBOT_IMAGE=ghcr.io/cosmiccubicle/pariahbot:1.1 in /opt/pariahbot-container/.env.

Under systemd, on Debian or Ubuntu, with Node.js 24+ installed by the script:

git clone --branch v1.1.0 https://github.com/CosmicCubicle/PariahBot.git
cd PariahBot
sudo ./deploy/setup.sh

See Host Installation.

On AWS or Azure, start with AWS Hosting or Azure Hosting.

Upgrading from 1.0.0

  • The database upgrades itself on startup. banned_words_enabled moves into the new feature-switch table; nothing else is needed.
  • Every feature stays on, except banned words, which keeps its current setting.
  • systemd installs: in your clone, run git pull, then rerun sudo ./deploy/setup.sh. Press Enter to keep each setting. If the auto-update job is on, it picks up this release by itself.

Full changes: v1.0.0...v1.1.0

Assets 3
Loading