[PR #729] feat: add Voy blueprint for self-hosted metasearch engine #14167

Open
opened 2026-06-17 06:21:26 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/729
Author: @LeoMartinDev
Created: 2/28/2026
Status: 🔄 Open

Base: canary ← Head: feat-add-voy-search-engine


📝 Commits (10+)

  • 07e7d59 feat: add Voy blueprint for self-hosted metasearch engine
  • ca9426f refactor(voy): migrate to template mounts and simplify docker compose
  • 0fd5ee4 fix(voy): mount searxng config volume and fix settings path
  • b2c2306 Update blueprints/voy/docker-compose.yml
  • 9a14ec7 Update blueprints/voy/template.toml
  • d491751 build(voy): pin docker images to specific versions
  • ed72f87 Merge branch 'feat-add-voy-search-engine' of github.com:LeoMartinDev/dokploy-templates into feat-add-voy-search-engine
  • 03b489e chore: remove duplicate "privacy" tag in meta.json
  • 79c0f8a chore(voy): rename service and volume from app to voy
  • 949ace1 chore(voy): update docker image tag from specific commit to latest

📊 Changes

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

View changed files

➕ blueprints/voy/docker-compose.yml (+57 -0)
➕ blueprints/voy/template.toml (+51 -0)
➕ blueprints/voy/voy.jpg (+0 -0)
📝 meta.json (+37 -18)

📄 Description

Introduce a new blueprint for Voy, a privacy-first metasearch engine built on SearXNG. The blueprint includes a Docker Compose configuration with Voy, SearXNG, and Valkey services, along with template variables and meta.json entry.

What is this PR about?

Add Voy, a self-hosted meta-search engine based on SearXNG : https://github.com/LeoMartinDev/voy

Checklist

Before submitting this PR, please make sure that:

Issues related (if applicable)

Close automatically the related issues using the keywords: closes #ISSUE_NUMBER

Screenshots or Videos

voy

Greptile Summary

Adds Voy blueprint for self-hosted metasearch engine with proper Docker Compose configuration, template variables, and meta.json entry. All previous review feedback has been addressed - service names now match blueprint folder, Docker images are pinned to specific versions, and duplicate tags removed.

Major changes:

  • New Voy blueprint with multi-service Docker Compose setup (Voy, SearXNG, Valkey)
  • Proper version pinning for security (b80c0f7, 2026.3.1-162c04a1c, 8-alpine)
  • Template configuration with domain routing, environment variables, and SearXNG settings mount
  • Meta.json entry with appropriate tags for discoverability

Issue found:

  • Version mismatch between meta.json (0.1.0) and Docker image tag (b80c0f7) violates AGENTS.md requirement that these must match

Confidence Score: 3/5

  • Safe to merge after fixing version mismatch - implementation follows Dokploy conventions and addresses all previous feedback
  • Score reflects well-structured implementation with proper security practices (pinned versions, no hardcoded secrets), but version mismatch between meta.json and docker-compose.yml must be resolved per AGENTS.md requirements before merge
  • meta.json requires version correction to match Docker image tag

Last reviewed commit: 79c0f8a

Context used:

  • Rule from dashboard - 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/729 **Author:** [@LeoMartinDev](https://github.com/LeoMartinDev) **Created:** 2/28/2026 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `feat-add-voy-search-engine` --- ### 📝 Commits (10+) - [`07e7d59`](https://github.com/Dokploy/templates/commit/07e7d59dbfb1965103308ea3a642f668ee238466) feat: add Voy blueprint for self-hosted metasearch engine - [`ca9426f`](https://github.com/Dokploy/templates/commit/ca9426f4233300fc1d660502eb8394d122fc70d5) refactor(voy): migrate to template mounts and simplify docker compose - [`0fd5ee4`](https://github.com/Dokploy/templates/commit/0fd5ee4f9dcbed459118f95c85c62f40e3fb2c69) fix(voy): mount searxng config volume and fix settings path - [`b2c2306`](https://github.com/Dokploy/templates/commit/b2c23064214557f19cfb075b83747640f9768df1) Update blueprints/voy/docker-compose.yml - [`9a14ec7`](https://github.com/Dokploy/templates/commit/9a14ec7410a5b532342316042b34d697176e2f6e) Update blueprints/voy/template.toml - [`d491751`](https://github.com/Dokploy/templates/commit/d491751cf6984db4642649c154e3dd56299f44a6) build(voy): pin docker images to specific versions - [`ed72f87`](https://github.com/Dokploy/templates/commit/ed72f87f0f37238023dd1e11c5b5bf940357c699) Merge branch 'feat-add-voy-search-engine' of github.com:LeoMartinDev/dokploy-templates into feat-add-voy-search-engine - [`03b489e`](https://github.com/Dokploy/templates/commit/03b489e6ba837568fb656245c629956a075e20dd) chore: remove duplicate "privacy" tag in meta.json - [`79c0f8a`](https://github.com/Dokploy/templates/commit/79c0f8aa0fb79c4c5af0547e7838acf9c0993960) chore(voy): rename service and volume from app to voy - [`949ace1`](https://github.com/Dokploy/templates/commit/949ace1119285b1388de920289a199062c7e0441) chore(voy): update docker image tag from specific commit to latest ### 📊 Changes **4 files changed** (+145 additions, -18 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/voy/docker-compose.yml` (+57 -0) ➕ `blueprints/voy/template.toml` (+51 -0) ➕ `blueprints/voy/voy.jpg` (+0 -0) 📝 `meta.json` (+37 -18) </details> ### 📄 Description Introduce a new blueprint for Voy, a privacy-first metasearch engine built on SearXNG. The blueprint includes a Docker Compose configuration with Voy, SearXNG, and Valkey services, along with template variables and meta.json entry. ## What is this PR about? Add Voy, a self-hosted meta-search engine based on SearXNG : https://github.com/LeoMartinDev/voy ## 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. ## Issues related (if applicable) Close automatically the related issues using the keywords: `closes #ISSUE_NUMBER` ## Screenshots or Videos ![voy](https://github.com/user-attachments/assets/aad4571e-8a93-4b4e-b1f7-b3398fe14238) <!-- greptile_comment --> <h3>Greptile Summary</h3> Adds Voy blueprint for self-hosted metasearch engine with proper Docker Compose configuration, template variables, and meta.json entry. All previous review feedback has been addressed - service names now match blueprint folder, Docker images are pinned to specific versions, and duplicate tags removed. **Major changes:** - New Voy blueprint with multi-service Docker Compose setup (Voy, SearXNG, Valkey) - Proper version pinning for security (`b80c0f7`, `2026.3.1-162c04a1c`, `8-alpine`) - Template configuration with domain routing, environment variables, and SearXNG settings mount - Meta.json entry with appropriate tags for discoverability **Issue found:** - Version mismatch between `meta.json` (`0.1.0`) and Docker image tag (`b80c0f7`) violates AGENTS.md requirement that these must match <h3>Confidence Score: 3/5</h3> - Safe to merge after fixing version mismatch - implementation follows Dokploy conventions and addresses all previous feedback - Score reflects well-structured implementation with proper security practices (pinned versions, no hardcoded secrets), but version mismatch between meta.json and docker-compose.yml must be resolved per AGENTS.md requirements before merge - `meta.json` requires version correction to match Docker image tag <sub>Last reviewed commit: 79c0f8a</sub> <!-- greptile_other_comments_section --> **Context used:** - Rule 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>
GiteaMirror added the pull-request label 2026-06-17 06:21:26 -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#14167