github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-03-12 10:05:25 -05:00
Code Issues 155 Packages Projects Releases Wiki Activity

[PR #258] [MERGED] Update Checkmate blueprint with new backend image and configuration #317

New Issue
Closed
opened 2025-11-22 20:35:05 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-22 20:35:05 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/258
Author: @jaainil
Created: 7/31/2025
Status: ✅ Merged
Merged: 8/11/2025
Merged by: @Siumauricio

Base: main ← Head: fix/update-checkmate-template

📝 Commits (3)

  • 9cd15c5 Update Checkmate blueprint with new backend image and configuration
  • 5af7f09 Merge branch 'main' into fix/update-checkmate-template
  • 26f98ec Merge branch 'main' into fix/update-checkmate-template

📊 Changes

3 files changed (+37 additions, -37 deletions)

View changed files

📝 blueprints/checkmate/docker-compose.yml (+21 -31)
📝 blueprints/checkmate/template.toml (+15 -5)
📝 meta.json (+1 -1)

📄 Description

What is this PR about?

New PR for Checkmate template.

This update replaces outdated Docker Hub images with the latest GitHub-hosted versions from Bluewave Labs. It also updates the docker-compose.yml and template.toml files to align with current best practices and the official Checkmate documentation. The new configuration improves reliability and ensures compatibility with Dokploy’s environment variable and volume handling.

Checklist

Before submitting this PR, please make sure that:

Issues related (if applicable)

Closes #237

🔄 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/258 **Author:** [@jaainil](https://github.com/jaainil) **Created:** 7/31/2025 **Status:** ✅ Merged **Merged:** 8/11/2025 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `main` ← **Head:** `fix/update-checkmate-template` --- ### 📝 Commits (3) - [`9cd15c5`](https://github.com/Dokploy/templates/commit/9cd15c5f6381612ba7f3ff61176ca897c91bb6e3) Update Checkmate blueprint with new backend image and configuration - [`5af7f09`](https://github.com/Dokploy/templates/commit/5af7f098e5c83d632eee15a61939f0d874cb58e4) Merge branch 'main' into fix/update-checkmate-template - [`26f98ec`](https://github.com/Dokploy/templates/commit/26f98ec07c125da3aa74afe57a32b006133e38cb) Merge branch 'main' into fix/update-checkmate-template ### 📊 Changes **3 files changed** (+37 additions, -37 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/checkmate/docker-compose.yml` (+21 -31) 📝 `blueprints/checkmate/template.toml` (+15 -5) 📝 `meta.json` (+1 -1) </details> ### 📄 Description ## What is this PR about? New PR for **Checkmate** template. This update replaces outdated Docker Hub images with the latest GitHub-hosted versions from Bluewave Labs. It also updates the `docker-compose.yml` and `template.toml` files to align with current best practices and the official Checkmate documentation. The new configuration improves reliability and ensures compatibility with Dokploy’s environment variable and volume handling. ## Checklist Before submitting this PR, please make sure that: - [x] I have read the suggestions in the README.md file [[Dokploy Templates README](https://github.com/Dokploy/templates?tab=readme-ov-file#general-suggestions-when-creating-a-template)](https://github.com/Dokploy/templates?tab=readme-ov-file#general-suggestions-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) Closes #237 --- <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 2025-11-22 20:35:05 -06: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#317
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?