[*] 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 Dokploy template for Onyx, a self-hostable Chat UI with RAG, MCP, and LLM integration features. The template consists of a 12-service Docker Compose setup (API server, background worker, web server, model servers, PostgreSQL, Vespa, Redis, MinIO, nginx, and code-interpreter), a template.toml with extensive environment configuration and nginx config file mounts, a logo, and the meta.json entry.
Key issues found:
Hardcoded default credentials: Postgres and MinIO use static default values instead of Dokploy's secret generation helpers, violating the project's security conventions from AGENTS.md
Nginx volume mount paths: The nginx service mounts files from ../files/volumes/data/nginx/... — verify these relative paths resolve correctly to the [[config.mounts]] files defined in template.toml, as a mismatch would prevent nginx from starting
Missing version: "3.8": AGENTS.md requires Docker Compose files to specify this version, which is absent from this template
build: sections and env_file: references: The docker-compose includes build: contexts pointing to GitHub repos and env_file: .env on every service — neither is functional in a Dokploy deployment and adds unnecessary noise
Missing trailing newline in docker-compose.yml
Confidence Score: 2/5
This PR needs changes before merging — hardcoded credentials and potentially broken nginx volume paths should be addressed
Score of 2 reflects the hardcoded default credentials (security concern per AGENTS.md), the potentially broken nginx volume mount paths that could prevent the service from starting, and multiple deviations from project conventions (missing version directive, build sections, env_file references). The meta.json entry and template.toml structure are otherwise well-formed.
🔄 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/707
**Author:** [@samiralavi](https://github.com/samiralavi)
**Created:** 2/10/2026
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `onyx-template`
---
### 📝 Commits (5)
- [`a1b5b0e`](https://github.com/Dokploy/templates/commit/a1b5b0ee10f6c43684d9f9a8360bc812f74e0c46) add onyx app
- [`556d444`](https://github.com/Dokploy/templates/commit/556d444787cf8bddc5ec3301e9e67243943f76af) fix spaces in the template env variables.
- [`66dc3ea`](https://github.com/Dokploy/templates/commit/66dc3ea02e0934ceae7c64223c5c11c70af7216c) fix spaces in the template env variables.
- [`0ce1ee8`](https://github.com/Dokploy/templates/commit/0ce1ee8f05dc4711cd344d9efb9e86e439429e1e) fix spaces in the template env variables.
- [`8b81825`](https://github.com/Dokploy/templates/commit/8b81825c027a48ab421258d72c359450d54f75f9) add nginx configuration
### 📊 Changes
**4 files changed** (+990 additions, -0 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/onyx/OnyxLogo.jpg` (+0 -0)
➕ `blueprints/onyx/docker-compose.yml` (+538 -0)
➕ `blueprints/onyx/template.toml` (+434 -0)
📝 `meta.json` (+18 -0)
</details>
### 📄 Description
## What is this PR about?
New PR of Onyx
## 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_comment -->
<h3>Greptile Summary</h3>
This PR adds a new Dokploy template for [Onyx](https://www.onyx.app/), a self-hostable Chat UI with RAG, MCP, and LLM integration features. The template consists of a 12-service Docker Compose setup (API server, background worker, web server, model servers, PostgreSQL, Vespa, Redis, MinIO, nginx, and code-interpreter), a `template.toml` with extensive environment configuration and nginx config file mounts, a logo, and the `meta.json` entry.
**Key issues found:**
- **Hardcoded default credentials**: Postgres and MinIO use static default values instead of Dokploy's secret generation helpers, violating the project's security conventions from AGENTS.md
- **Nginx volume mount paths**: The nginx service mounts files from `../files/volumes/data/nginx/...` — verify these relative paths resolve correctly to the `[[config.mounts]]` files defined in `template.toml`, as a mismatch would prevent nginx from starting
- **Missing `version: "3.8"`**: AGENTS.md requires Docker Compose files to specify this version, which is absent from this template
- **`build:` sections and `env_file:` references**: The docker-compose includes `build:` contexts pointing to GitHub repos and `env_file: .env` on every service — neither is functional in a Dokploy deployment and adds unnecessary noise
- **Missing trailing newline** in `docker-compose.yml`
<h3>Confidence Score: 2/5</h3>
- This PR needs changes before merging — hardcoded credentials and potentially broken nginx volume paths should be addressed
- Score of 2 reflects the hardcoded default credentials (security concern per AGENTS.md), the potentially broken nginx volume mount paths that could prevent the service from starting, and multiple deviations from project conventions (missing version directive, build sections, env_file references). The meta.json entry and template.toml structure are otherwise well-formed.
- `blueprints/onyx/template.toml` (hardcoded credentials), `blueprints/onyx/docker-compose.yml` (nginx volume paths, convention violations)
<sub>Last reviewed commit: 8b81825</sub>
<!-- greptile_other_comments_section -->
<sub>(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!</sub>
**Context used:**
- Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))
<!-- /greptile_comment -->
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/707
Author: @samiralavi
Created: 2/10/2026
Status: 🔄 Open
Base:
main← Head:onyx-template📝 Commits (5)
a1b5b0eadd onyx app556d444fix spaces in the template env variables.66dc3eafix spaces in the template env variables.0ce1ee8fix spaces in the template env variables.8b81825add nginx configuration📊 Changes
4 files changed (+990 additions, -0 deletions)
View changed files
➕
blueprints/onyx/OnyxLogo.jpg(+0 -0)➕
blueprints/onyx/docker-compose.yml(+538 -0)➕
blueprints/onyx/template.toml(+434 -0)📝
meta.json(+18 -0)📄 Description
What is this PR about?
New PR of Onyx
Checklist
Before submitting this PR, please make sure that:
Screenshots or Videos
Greptile Summary
This PR adds a new Dokploy template for Onyx, a self-hostable Chat UI with RAG, MCP, and LLM integration features. The template consists of a 12-service Docker Compose setup (API server, background worker, web server, model servers, PostgreSQL, Vespa, Redis, MinIO, nginx, and code-interpreter), a
template.tomlwith extensive environment configuration and nginx config file mounts, a logo, and themeta.jsonentry.Key issues found:
../files/volumes/data/nginx/...— verify these relative paths resolve correctly to the[[config.mounts]]files defined intemplate.toml, as a mismatch would prevent nginx from startingversion: "3.8": AGENTS.md requires Docker Compose files to specify this version, which is absent from this templatebuild:sections andenv_file:references: The docker-compose includesbuild:contexts pointing to GitHub repos andenv_file: .envon every service — neither is functional in a Dokploy deployment and adds unnecessary noisedocker-compose.ymlConfidence Score: 2/5
blueprints/onyx/template.toml(hardcoded credentials),blueprints/onyx/docker-compose.yml(nginx volume paths, convention violations)Last reviewed commit:
8b81825(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!
Context used:
dashboard- AGENTS.md (source)🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.