[PR #825] Add qui A fast, modern web interface for qBittorrent. Manage multiple qBittorrent instances from a single, lightweight application built by autobrr #4293

New Issue

GiteaMirror · 2026-04-30T06:51:43-05:00

GiteaMirror commented

2026-04-30 06:51:43 -05:00

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/825
Author: @Yuri-NagaSaki
Created: 4/28/2026
Status: 🔄 Open

Base: canary ← Head: add-qui

📝 Commits (5)

ab8f522 feat: add qui template
f05f88e fix(qui): use latest image tag
fc25557 revert: restore duplicate strapi entry removed by dedupe script
c495e7f fix: deduplicate meta.json to pass CI validation
3c64d99 fix(qui): replace logo with autobrr org avatar (128x128)

📊 Changes

4 files changed (+41 additions, -18 deletions)

View changed files

➕ blueprints/qui/docker-compose.yml (+13 -0)
➕ blueprints/qui/qui.png (+0 -0)
➕ blueprints/qui/template.toml (+9 -0)
📝 meta.json (+19 -18)

📄 Description

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)

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)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Dokploy/templates/pull/825 **Author:** [@Yuri-NagaSaki](https://github.com/Yuri-NagaSaki) **Created:** 4/28/2026 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `add-qui` --- ### 📝 Commits (5) - [`ab8f522`](https://github.com/Dokploy/templates/commit/ab8f522175a2de8cb0afd911ab80ab84d4a335c6) feat: add qui template - [`f05f88e`](https://github.com/Dokploy/templates/commit/f05f88edd49da3ba76a9b51ef75fb32e74ba2265) fix(qui): use latest image tag - [`fc25557`](https://github.com/Dokploy/templates/commit/fc25557504d67f1cb7063a4ffd7c708411c26770) revert: restore duplicate strapi entry removed by dedupe script - [`c495e7f`](https://github.com/Dokploy/templates/commit/c495e7fa5c3da338197d523fc46fa0e7f02362a7) fix: deduplicate meta.json to pass CI validation - [`3c64d99`](https://github.com/Dokploy/templates/commit/3c64d999a84fdfb3fb3e8cff6f56aa6e9a1d6c82) fix(qui): replace logo with autobrr org avatar (128x128) ### 📊 Changes **4 files changed** (+41 additions, -18 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/qui/docker-compose.yml` (+13 -0) ➕ `blueprints/qui/qui.png` (+0 -0) ➕ `blueprints/qui/template.toml` (+9 -0) 📝 `meta.json` (+19 -18) </details> ### 📄 Description ## What is this PR about? Add qui templates ## Checklist Before submitting this PR, please make sure that: - [x] 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 - [x] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong. - [x] I have added tests that demonstrate that my correction works or that my new feature works. ## Screenshots or Videos <img width="3155" height="1483" alt="image" src="https://github.com/user-attachments/assets/5e083f87-ed41-47bb-8e98-7e02ad1bd7c9" /> <img width="1819" height="1348" alt="1cd6f8a29182a0852cec001a7db4d171" src="https://github.com/user-attachments/assets/9b3f96e4-a204-4444-a422-3013aacab6c2" />  <h3>Greptile Summary</h3> 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. <h3>Confidence Score: 3/5</h3> 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)  <details><summary><h3>Comments Outside Diff (1)</h3></summary> 1. `meta.json`, line 5971-5989 ([link](https://github.com/dokploy/templates/blob/c495e7fa5c3da338197d523fc46fa0e7f02362a7/meta.json#L5971-L5989)) <a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=7" align="top"></a> **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: ```json { "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" ] } ``` </details>  <sub>Reviews (3): Last reviewed commit: ["fix(qui): replace logo with autobrr org ..."](https://github.com/dokploy/templates/commit/3c64d999a84fdfb3fb3e8cff6f56aa6e9a1d6c82) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30017828)</sub> **Context used:** - Context used - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))  --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-30 06:51:43 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#4293