github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-07-16 13:24:11 -05:00
Code Issues 3.0k Packages Projects Releases Wiki Activity

[PR #722] [MERGED] Update Meilisearch 1.35.1 and fix Cyberchef logo #16062

New Issue
Closed
opened 2026-07-14 23:08:00 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-07-14 23:08:00 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/722
Author: @jdjimenez2312
Created: 2/21/2026
Status: ✅ Merged
Merged: 5/12/2026
Merged by: @Siumauricio

Base: canary ← Head: Update-Meilisearch-and-Fix-Cyberchef

📝 Commits (2)

  • 34c0ca3 fix: update CyberChef logo from SVG to PNG and remove old SVG file
  • e78305f fix: update Meilisearch version to v1.35.1

📊 Changes

5 files changed (+4 additions, -6 deletions)

View changed files

➕ blueprints/cyberchef/cyberchef.png (+0 -0)
➖ blueprints/cyberchef/cyberchef.svg (+0 -0)
📝 blueprints/meilisearch/docker-compose.yml (+1 -2)
📝 blueprints/meilisearch/template.toml (+1 -2)
📝 meta.json (+2 -2)

📄 Description

What is this PR about?

New PR of meilisearch and cyberchef

Checklist

Before submitting this PR, please make sure that:

Greptile Summary

Updated Meilisearch from v1.8.3 to v1.35.1 and replaced CyberChef logo from SVG to PNG format.

  • Updated Meilisearch Docker image version in docker-compose.yml and meta.json
  • Removed MEILI_ENV environment variable from Meilisearch configuration
  • Replaced CyberChef logo from SVG to PNG format and updated reference in meta.json

Confidence Score: 4/5

  • Safe to merge after fixing the missing restart policy in Meilisearch docker-compose.yml
  • The changes are straightforward version updates and logo format change. However, the Meilisearch docker-compose.yml is missing the required restart policy per project guidelines, which is a critical requirement for production deployments. Once this is fixed, the PR will be safe to merge.
  • Pay attention to blueprints/meilisearch/docker-compose.yml to ensure restart policy is added

Last reviewed commit: e78305f

Context used:

  • Context 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/722 **Author:** [@jdjimenez2312](https://github.com/jdjimenez2312) **Created:** 2/21/2026 **Status:** ✅ Merged **Merged:** 5/12/2026 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `canary` ← **Head:** `Update-Meilisearch-and-Fix-Cyberchef` --- ### 📝 Commits (2) - [`34c0ca3`](https://github.com/Dokploy/templates/commit/34c0ca30cbb1fb9287fe944cba0b3c6cb33e60a2) fix: update CyberChef logo from SVG to PNG and remove old SVG file - [`e78305f`](https://github.com/Dokploy/templates/commit/e78305f2661aa7bf14cdf85ef7055d968f944f85) fix: update Meilisearch version to v1.35.1 ### 📊 Changes **5 files changed** (+4 additions, -6 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/cyberchef/cyberchef.png` (+0 -0) ➖ `blueprints/cyberchef/cyberchef.svg` (+0 -0) 📝 `blueprints/meilisearch/docker-compose.yml` (+1 -2) 📝 `blueprints/meilisearch/template.toml` (+1 -2) 📝 `meta.json` (+2 -2) </details> ### 📄 Description ## What is this PR about? New PR of meilisearch and cyberchef ## 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. <!-- greptile_comment --> <h3>Greptile Summary</h3> Updated Meilisearch from v1.8.3 to v1.35.1 and replaced CyberChef logo from SVG to PNG format. - Updated Meilisearch Docker image version in `docker-compose.yml` and `meta.json` - Removed `MEILI_ENV` environment variable from Meilisearch configuration - Replaced CyberChef logo from SVG to PNG format and updated reference in `meta.json` <h3>Confidence Score: 4/5</h3> - Safe to merge after fixing the missing restart policy in Meilisearch docker-compose.yml - The changes are straightforward version updates and logo format change. However, the Meilisearch docker-compose.yml is missing the required `restart` policy per project guidelines, which is a critical requirement for production deployments. Once this is fixed, the PR will be safe to merge. - Pay attention to `blueprints/meilisearch/docker-compose.yml` to ensure restart policy is added <sub>Last reviewed commit: e78305f</sub> <!-- greptile_other_comments_section --> **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>
GiteaMirror added the pull-request label 2026-07-14 23:08:00 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#16062
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?