Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] MaybeGrim Unraid Templates (NextExplorer, Forgejo Runner, LambData, Buzz, Pumpkin, DuskBot)

Featured Replies

This is the central support thread for MaybeGrim's Unraid Community Applications templates. Installation questions, template problems, update reports, and configuration help for every application below are welcome here.

Template repository: github.com/maybegrim/unraid-templates

Available templates:

  • NextExplorer — modern web-based file management

  • Forgejo Runner — Forgejo Actions workflow runner

  • LambData (formerly KilnDB) — self-hosted MySQL and MariaDB control plane

  • Buzz — collaborative workspace for people and AI agents

  • Pumpkin — high-performance Minecraft server written in Rust

  • DuskBot — self-hosted AI bots you text like contacts


NextExplorer

NextExplorer is a modern, self-hosted web interface for browsing and managing files on your server.

Installation notes: Search for NextExplorer in Community Applications. The web interface uses port 3000. Mount each Unraid share beneath /mnt/<Label> to make it available in the interface.

Private access: The template includes optional Tailscale Serve support so the web interface can remain available only to authorized devices on your tailnet.


Forgejo Runner

Forgejo Runner executes Forgejo Actions workflows and uses the official Forgejo runner image.

Initial setup:

  1. Generate /mnt/user/appdata/forgejo-runner/data/runner-config.yml.

  2. Create a runner in Forgejo and add its URL, UUID, and token under server.connections.

  3. Configure runner.labels for the environments required by your workflows.

  4. If jobs require Docker, set container.docker_host to automount.

Security warning: Access to the Docker socket effectively grants host-level control. Only run trusted workflows, actions, and container images.


LambData (formerly KilnDB)

Project: https://github.com/lambdatadb/lambdata

Container package: https://github.com/lambdatadb/lambdata/pkgs/container/lambdata

Image: ghcr.io/lambdatadb/lambdata:latest

Template: https://github.com/maybegrim/unraid-templates/blob/main/LambData/LambData.xml

Installation notes: Search for LambData in Community Applications. The web interface uses port 4317, and application data is persisted at /data. There are no default login credentials. A new installation asks for a one-time setup token, which is printed in the container log (click the container icon, then Logs).

The bundled MariaDB service is internal-only by default. If you deliberately expose it, set MariaDB Bind Address to 0.0.0.0 and publish port 3307 only on a trusted network.

Upgrading from KilnDB: The old image, ghcr.io/maybegrim/kilndb, no longer receives updates, so Unraid will not show an update for an existing KilnDB container. To move to LambData, back up your appdata folder, edit the container, change Repository to ghcr.io/lambdatadb/lambdata:latest, and keep the existing data path. Existing KILNDB_ variables continue to work. After the move, tables without a Data API policy refuse requests until you open that database's Data API, and application sign-up is off unless you had switched it on. Full notes: https://github.com/lambdatadb/lambdata/blob/main/docs/upgrading.md


Buzz

Buzz is a self-hosted workspace where people and AI agents collaborate through a Nostr relay, channels, threads, workflows, media, search, and Git events.

Requirements: Buzz is not a standalone one-container application. Configure PostgreSQL 17, Redis 7, and an S3-compatible object store such as MinIO before starting it, and create the S3 bucket first. The web interface and relay use port 3000; optional health and metrics endpoints use ports 8080 and 9102.

For a production-style installation, provide a stable 64-character relay private key and your 64-character lowercase Nostr owner public key. Keep authentication and relay membership enforcement enabled. Back up the relay key, PostgreSQL database, S3 bucket, and Git data path.

Private Tailscale access: Enable Tailscale in the template, set the Public Relay URL to the wss:// Tailscale hostname, and set the Public Media URL to the corresponding https:// hostname ending in /media.


Pumpkin

Pumpkin is a high-performance Minecraft server written entirely in Rust. The official container includes the server binary, so no Java runtime or Mojang server JAR is required.

Storage and ports:

  • Persistent server data and configuration: /pumpkin

  • Java Edition: TCP 25565

  • Java Query: UDP 25565

  • Bedrock Edition: UDP 19132

  • Optional RCON: TCP 25575

Development warning: Pumpkin is pre-release software under active development. Its Docker support is described upstream as experimental, the latest tag follows development, and Bedrock support remains work in progress. Keep tested backups of the complete /pumpkin directory before updating.

Private Tailscale access: Minecraft uses raw TCP and UDP rather than HTTP, so Tailscale Serve is not used. Players on your tailnet can connect directly to the Unraid server's Tailscale IP and the appropriate game port.

DuskBot
Project: https://github.com/DuskBotAI/duskbot
Container: https://github.com/maybegrim/unraid-templates/pkgs/container/duskbot
Image: ghcr.io/maybegrim/duskbot:latest
Template: https://raw.githubusercontent.com/maybegrim/unraid-templates/main/DuskBot/DuskBot.xml

DuskBot lets you create AI bots that you text like contacts. Each one has its own memory, files, a browser it can use, and scheduled routines. Bots run on AI subscriptions or API keys you already have. Claude Code and Codex come with the image, and you can add more engines under Settings → Engines.

About the image: DuskBot doesn’t publish a server image, so I build one from DuskBot’s own Dockerfile for each release and add a small Unraid layer: a built-in web proxy, an optional Cloudflare Tunnel, and PUID/PGID support. Please report problems with the image or template in this thread. Report bugs in DuskBot itself on its GitHub.

Install notes

  • Data is stored in /data (default /mnt/user/appdata/duskbot). This includes bots, chats, sign-ins to Claude and Codex, and paired devices. Back it up.

  • There’s no default login. Every browser has to be paired once. Open the container’s console and run duskbot pair, then open the link it prints or enter the code at /pair.

  • Sign in to Claude Code and Codex under Settings → Engines, or run duskbot-shell claude in the console.

  • On your network: use the Web UI at port 8799. It’s plain HTTP, so only use it on a network you trust, and never forward that port to the internet.

  • Tailscale: turn on the template’s Tailscale option (Serve is already set to port 8080). Set Public URL to the https://….ts.net address Unraid shows you.

  • Cloudflare Tunnel: create a tunnel in Cloudflare Zero Trust and paste its token into Cloudflare Tunnel Token. Add a public hostname with service HTTP and URL localhost:8080, then set Public URL to that hostname.

  • Webhooks work on every access path at /hooks/….

License: DuskBot uses the PolyForm Noncommercial 1.0.0 license. It’s free for personal and other noncommercial use. Commercial use needs a license from dusk.bot.


Getting support

If you run into an issue, reply here and include:

  • Your Unraid version

  • The application and template version or container image

  • Relevant container logs with secrets removed

  • Any changes made to the template

  • Whether this is a fresh installation or an existing container

Templates can also be installed manually from the XML links above. Community Applications availability and metadata updates follow its normal indexing process.

Edited by MaybeGrim
Added DuskBot.

  • MaybeGrim changed the title to [Support] MaybeGrim Unraid Templates — NextExplorer, Forgejo Runner & KilnDB
  • 3 months later...

Hi, thanks for your templates, but it seems the templates under community applications are outdated for forgejo -> it is still showing the old versions, which are "hardcoded" in the template.

Edited by Doublemyst

  • MaybeGrim changed the title to [Support] MaybeGrim Unraid Templates — NextExplorer, Forgejo Runner, KilnDB & Buzz
  • Author

Thanks for flagging this. I updated the public Forgejo Runner template on July 19, and it now uses:

data.forgejo.org/forgejo/runner:12

I verified that both the repository and the public raw XML currently show Runner 12:

https://raw.githubusercontent.com/maybegrim/unraid-templates/main/ForgejoRunner/ForgejoRunner.xml

If Community Applications is still displaying an older hardcoded tag, it appears its indexed metadata/cache has not refreshed yet. A manual installation from the template URL above will use Runner 12.

If this is an existing installed container, please also open Edit Container and check the Repository field, since a locally saved container configuration may retain its previous image tag instead of being overwritten by a later template update. You can change that field to data.forgejo.org/forgejo/runner:12 and apply the container update.

On 7/20/2026 at 7:28 AM, Doublemyst said:

Hi, thanks for your templates, but it seems the templates under community applications are outdated for forgejo -> it is still showing the old versions, which are "hardcoded" in the template.

If you can share the exact older version shown and whether this is a fresh CA install or an existing container, I can narrow down which cache/template layer is stale.

  • MaybeGrim changed the title to [Support] MaybeGrim Unraid Templates (NextExplorer, Forgejo Runner, LambData, Buzz, Pumpkin, DuskBot)

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.