Add Onyx template by samiralavi · Pull Request #707 · Dokploy/templates

samiralavi · 2026-02-10T16:17:44Z

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 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.
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:

Context from dashboard - AGENTS.md (source)

github-actions · 2026-02-10T16:18:37Z

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	`8b81825`

Siumauricio · 2026-02-10T22:13:07Z

Hey, I'm getting error to import the template in dokploy

samiralavi · 2026-02-11T14:31:49Z

@Siumauricio, the issue is now fixed. I have added the nginx configuration files, and it works well. I have tested it

Siumauricio · 2026-02-16T02:52:32Z

@greptile review

greptile-apps

_{4 files reviewed, 7 comments}

_{Edit Code Review Agent Settings | Greptile}

greptile-apps · 2026-02-16T02:57:02Z

blueprints/onyx/docker-compose.yml

+# For a complete production setup, refer to docker-compose.prod.yml
+# =============================================================================
+
+name: onyx


Missing version: "3.8" directive

Per the project's AGENTS.md conventions, Docker Compose files must specify version: "3.8". The name: onyx directive at line 37 is also not standard for Dokploy templates (only ~7 out of 374 templates use it), and may interfere with Dokploy's own project naming. Consider replacing with the required version directive or adding it above the name: line.

Context Used: Context from dashboard - AGENTS.md (source)

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

greptile-apps · 2026-02-16T02:57:03Z

blueprints/onyx/docker-compose.yml

+    build:
+      context: https://github.com/onyx-dot-app/onyx.git#main:backend
+      dockerfile: Dockerfile
+      args:
+        - ENABLE_CRAFT=${ENABLE_CRAFT:-false}


build: sections won't work in Dokploy

Multiple services (api_server, background, web_server, inference_model_server, indexing_model_server) include build: sections that reference a remote Git context. In a Dokploy deployment, these build: blocks are not used — Dokploy pulls pre-built images. While they're not harmful (Docker Compose will use image: if the build context is unavailable), they add significant noise to the template and could confuse users. Consider removing the build: sections from all services to keep the template focused on the Dokploy deployment workflow.

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

greptile-apps · 2026-02-16T02:57:04Z

blueprints/onyx/docker-compose.yml

+    env_file:
+      - path: .env
+        required: false


env_file references non-existent .env file

Every service in this compose file references env_file: .env with required: false. In a Dokploy deployment, environment variables are managed through template.toml's [config] env array, and there is no .env file present. While required: false means this won't cause a startup failure, it's misleading and unnecessary in the Dokploy context. Consider removing all env_file: blocks.

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

greptile-apps · 2026-02-16T02:57:05Z

blueprints/onyx/docker-compose.yml

+    volumes:
+      - ../files/volumes/data/nginx/app.conf.template:/etc/nginx/conf.d/app.conf.template
+      - ../files/volumes/data/nginx/mcp.conf.inc.template:/etc/nginx/conf.d/mcp.conf.inc.template
+      - ../files/volumes/data/nginx/mcp_upstream.conf.inc.template:/etc/nginx/conf.d/mcp_upstream.conf.inc.template
+      - ../files/volumes/data/nginx/run-nginx.sh:/etc/nginx/conf.d/run-nginx.sh


Nginx volume mounts use host-relative paths

The nginx service mounts configuration files from ../files/volumes/data/nginx/.... In Dokploy, these files are provided via [[config.mounts]] in template.toml, which creates them at paths like /volumes/data/nginx/... relative to the service's file mount root. However, the docker-compose references use ../files/volumes/data/nginx/... — verify that Dokploy correctly resolves these relative paths to the mounted files defined in the template.toml. If they don't match, nginx will fail to start because it can't find its configuration files.

greptile-apps · 2026-02-16T02:57:06Z

blueprints/onyx/docker-compose.yml

+    # Below is needed for the `docker-out-of-docker` execution mode
+    user: root
+    volumes:
+      - /var/run/docker.sock:/var/run/docker.sock


Docker socket mount with root user

The code-interpreter service runs as user: root and mounts the host Docker socket. This gives this container full control over the host's Docker daemon. While other templates in the repo also mount the Docker socket for specific use cases (portainer, windmill, etc.), combining it with user: root and an always-on restart: unless-stopped service that conditionally runs tail -f /dev/null when disabled is worth noting. Users should be aware of this security implication.

greptile-apps · 2026-02-16T02:57:07Z

blueprints/onyx/template.toml

+'POSTGRES_USER=postgres',
+'POSTGRES_PASSWORD=password',


Use Dokploy helpers for credentials

The Postgres and MinIO credentials in this template use static, well-known default values. Per AGENTS.md guidelines, templates should use Dokploy's variable system with helpers like ${password:32} instead of hardcoding credentials. Most other templates in this repo follow this pattern — see blueprints/windmill/template.toml or blueprints/zitadel/template.toml for examples. This also applies to the MinIO-related values on lines 78-82.

Context Used: Context from dashboard - AGENTS.md (source)

greptile-apps · 2026-02-16T02:57:08Z

blueprints/onyx/docker-compose.yml

+  inference_model_server_logs:
+  indexing_model_server_logs:
+  # Shared volume for persistent document storage (Craft file-system mode)
+  file-system:


Missing trailing newline

The file is missing a newline at the end. The git diff shows \ No newline at end of file on the last line. This is a minor issue but can cause problems with some tools and produces noisy diffs when lines are later appended.

Suggested change

file-system:

file-system:

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

add onyx app

a1b5b0e

samiralavi changed the base branch from canary to main February 10, 2026 16:18

github-actions bot deployed to Preview February 10, 2026 16:18 View deployment

fix spaces in the template env variables.

556d444

github-actions bot deployed to Preview February 10, 2026 16:22 View deployment

fix spaces in the template env variables.

66dc3ea

github-actions bot deployed to Preview February 10, 2026 16:32 View deployment

fix spaces in the template env variables.

0ce1ee8

github-actions bot deployed to Preview February 10, 2026 16:35 View deployment

samiralavi changed the title ~~Onyx template~~ Add Onyx template Feb 10, 2026

add nginx configuration

8b81825

github-actions bot deployed to Preview February 11, 2026 14:31 View deployment

greptile-apps bot reviewed Feb 16, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add Onyx template#707

Add Onyx template#707
samiralavi wants to merge 5 commits intoDokploy:mainfrom
samiralavi:onyx-template

samiralavi commented Feb 10, 2026 •

edited by greptile-apps bot

Loading

Uh oh!

github-actions bot commented Feb 10, 2026 •

edited

Loading

Uh oh!

Siumauricio commented Feb 10, 2026

Uh oh!

samiralavi commented Feb 11, 2026

Uh oh!

Siumauricio commented Feb 16, 2026

Uh oh!

greptile-apps bot left a comment

Uh oh!

greptile-apps bot Feb 16, 2026

Uh oh!

greptile-apps bot Feb 16, 2026

Uh oh!

greptile-apps bot Feb 16, 2026

Uh oh!

greptile-apps bot Feb 16, 2026

Uh oh!

greptile-apps bot Feb 16, 2026

Uh oh!

greptile-apps bot Feb 16, 2026

Uh oh!

greptile-apps bot Feb 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

		'POSTGRES_USER=postgres',
		'POSTGRES_PASSWORD=password',

Conversation

samiralavi commented Feb 10, 2026 • edited by greptile-apps bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What is this PR about?

Checklist

Screenshots or Videos

Greptile Summary

Confidence Score: 2/5

Uh oh!

github-actions bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Uh oh!

Siumauricio commented Feb 10, 2026

Uh oh!

samiralavi commented Feb 11, 2026

Uh oh!

Siumauricio commented Feb 16, 2026

Uh oh!

greptile-apps bot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

samiralavi commented Feb 10, 2026 •

edited by greptile-apps bot

Loading

github-actions bot commented Feb 10, 2026 •

edited

Loading