Add qui A fast, modern web interface for qBittorrent. Manage multiple qBittorrent instances from a single, lightweight application built by autobrr

[Yuri-NagaSaki]

What is this PR about?

Add qui templates

Checklist

Before submitting this PR, please make sure that:

• I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template
• I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
• I have added tests that demonstrate that my correction works or that my new feature works.

Screenshots or Videos

Greptile Summary

This PR adds a new template for qui, a web interface for managing multiple qBittorrent instances built by autobrr. The blueprint files (docker-compose.yml, template.toml, logo) are structurally correct and follow Dokploy conventions.

Previous review comments flagging the unpinned :latest image tag and the accidental removal of the Strapi entry from meta.json remain unaddressed — both issues need to be resolved before merging.

Confidence Score: 3/5

Not safe to merge — the Strapi template entry was inadvertently deleted from meta.json, and the Docker image remains unpinned to a specific version.

Two P1 issues flagged in prior review rounds remain unaddressed: (1) accidental removal of the Strapi entry from meta.json (a production-visible regression for existing users) and (2) the Docker image pinned to :latest instead of a specific release tag, violating the repo's explicit supply-chain security policy. Score is pulled below the P1 ceiling of 4 because both issues must be fixed simultaneously.

meta.json (Strapi deletion + version field), blueprints/qui/docker-compose.yml (unpinned image tag)

Comments Outside Diff (1)

1. meta.json, line 5971-5989 (link)

   Accidental removal of existing Strapi template entry

   The Strapi entry has been deleted from meta.json in this PR, but this PR is only intended to add qui. The blueprints/strapi/ directory still exists in the repository, so removing its registry entry will make the Strapi template invisible to Dokploy users. This appears to be an inadvertent side-effect of a merge conflict or manual edit near this section of the file.

   Please restore the Strapi entry:

   {
     "id": "strapi",
     "name": "Strapi",
     "version": "v5.33.0",
     "description": "Open-source headless CMS to build powerful APIs with built-in content management.",
     "logo": "strapi.svg",
     "links": {
       "github": "https://github.com/strapi/strapi",
       "discord": "https://discord.com/invite/strapi",
       "docs": "https://docs.strapi.io",
       "website": "https://strapi.io"
     },
     "tags": [
       "headless",
       "cms",
       "content-management"
     ]
   }

_{Reviews (3): Last reviewed commit: "fix(qui): replace logo with autobrr org ..." | Re-trigger Greptile}

Context used:

• Context used - AGENTS.md (source)

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	3c64d99

[greptile-apps]

Docker image not pinned to a specific version

Using :latest is explicitly discouraged by this repo's guidelines. It prevents reproducible deployments and creates a supply chain risk — a compromised or breaking upstream release will silently affect all existing Dokploy instances. Pin the image to a specific release tag (e.g., ghcr.io/autobrr/qui:v0.x.y) and update version in meta.json to match.

[greptile-apps]

version should match a pinned image tag

The guidelines require version in meta.json to match the Docker image tag used in docker-compose.yml. Once the image is pinned to a specific release (e.g., v0.x.y), update this field to reflect that exact version.

[Copilot]

Pull request overview

Adds a new Dokploy blueprint for qui (autobrr’s lightweight multi-instance qBittorrent web UI) by introducing its compose/template configuration and registering it in the central meta.json index.

Changes:

• Add blueprints/qui/docker-compose.yml to deploy qui with a persistent config volume.
• Add blueprints/qui/template.toml to map a domain to the qui service on port 7476.
• Add a qui entry to meta.json (metadata, links, tags, logo).

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 3 comments.

File	Description
meta.json	Registers the new qui template in the template catalog.
blueprints/qui/template.toml	Adds domain routing configuration for the qui service.
blueprints/qui/docker-compose.yml	Defines the qui service and persistent storage volume.

[Copilot]

The template is using a floating latest version in meta.json. For reproducible deployments and to avoid breaking changes when upstream releases, consider pinning this to a specific qui release and keeping it in sync with the Docker image tag used in the compose file.

Suggested change

	"version": "latest",
	"version": "1.0.0",

[Copilot]

The Docker image tag is set to :latest, which makes deployments non-deterministic and can break unexpectedly when the upstream image changes. Prefer pinning to a specific, known-good release tag (and align meta.json's version with it).

Suggested change

	image: ghcr.io/autobrr/qui:latest
	image: ghcr.io/autobrr/qui:v1.0.0

[Yuri-NagaSaki]

They don't have any specific release tags.

[Copilot]

The PR description checklist indicates tests were added, but this change set only adds a new blueprint and meta entry. Please either add the referenced tests or update the checklist to avoid confusion for reviewers/maintainers.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 4 changed files in this pull request and generated no new comments.