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

• KilnDB — self-hosted MySQL and MariaDB control plane

• Buzz — collaborative workspace for people and AI agents

• Pumpkin — high-performance Minecraft server written in Rust

---

NextExplorer

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

• Project: github.com/nxzai/NextExplorer

• Container: hub.docker.com/r/nxzai/explorer

• Documentation: explorer.nxz.ai

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.

• Project: code.forgejo.org/forgejo/runner

• Image: data.forgejo.org/forgejo/runner:12

• Documentation: Forgejo runner installation

• Template: ForgejoRunner.xml

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.

---

KilnDB

KilnDB is a self-hosted MySQL and MariaDB control plane with a web console, Data API, Auth, Realtime, Functions, and Storage.

• Project: github.com/maybegrim/KilnDB

• Container package: ghcr.io/maybegrim/kilndb

• Image: ghcr.io/maybegrim/kilndb:latest

• Template: KilnDB.xml

Installation notes: Search for KilnDB in Community Applications. The web interface uses port 4317, and application data is persisted at /data. There are no default login credentials.

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

---

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.

• Project and documentation: github.com/block/buzz

• Container package: ghcr.io/block/buzz

• Image: ghcr.io/block/buzz:latest

• Template: Buzz.xml

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.

• Project: github.com/Pumpkin-MC/Pumpkin

• Documentation: docs.pumpkinmc.org

• Container package: ghcr.io/pumpkin-mc/pumpkin

• Image: ghcr.io/pumpkin-mc/pumpkin:latest

• Template: Pumpkin.xml

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.

---

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 Thursday at 09:43 PM1 day by MaybeGrim
Added Pumpkin and reorganized the application support information.

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 Monday at 11:28 AM4 days by Doublemyst

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.