[Feature]: unraid native app store

[lfnovo]

Status (Sep 5, 2026): parked — waiting for a contributor. Converted from issue #268 under the Open Contribution model: Issues are for work we've committed to; Ideas are for things we'd welcome but haven't scheduled. Nobody has picked this up since Nov 2025, so it belongs here until someone does.

What are you trying to do?

Install Open Notebook on Unraid from the Community Applications store, the way that community installs most things: pick a template, fill in a few fields, click Apply.

What feels difficult or missing today?

There is no Unraid template. Users have to translate docker-compose.yml by hand into two Unraid containers (Open Notebook + SurrealDB) and wire the network, volumes and env vars themselves.

What outcome would help?

A Community Applications XML template (or a pair) that a maintainer or community member publishes and keeps in sync with releases.

How do you handle this today?

Manual container setup on Unraid, or running Docker Compose outside the Unraid app model.

Additional context, examples, or possible directions

• Topology is the main open question. The single-container image is deprecated and goes away in v2 (see docs), so "one container with everything" is not an option. That leaves a two-container template, which Community Applications handles less gracefully.
• Env vars & volumes should map 1:1 from the current docker-compose.yml.
• Precedent: the EasyPanel template ([Feature]: Create EasyPanel Templates #189) lives in examples/easypanel/ and is maintained by that community. The same arrangement would work here: template in examples/unraid/ or in a community repo, with a link from the install docs.
• Ownership is the real gate. We won't maintain an Unraid template ourselves; we will review, merge and link one that a contributor maintains.

How would you like to participate?

If you run Unraid and want to build the template, say so here. Once someone commits, this graduates to a ready Issue with the scope above.

[lfnovo]

Marking as needs-design. The request (an Unraid Community Apps template for Open Notebook) makes sense, but it's currently a one-liner. Before a contributor can pick it up, the design phase should settle:

• Template format/target: an Unraid CA XML template submitted to the Community Applications repo.
• Topology: single-container vs multi-container — Open Notebook needs SurrealDB; decide whether to bundle (single image) or template the full stack.
• Env vars & volumes: map the required configuration and persistent volumes from the existing docker-compose as the basis.
• Submission/maintenance path: how the template gets published to Community Applications and who maintains it.

Reference #189 (EasyPanel template) for how a similar deployment-template effort was handled. Once the topology and template contents are decided, this can move to ready.