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

[PR #255] [MERGED] Refactor Blinko blueprint configuration and environment handling #314

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

📋 Pull Request Information

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

Base: main ← Head: fix/blinko-default-port-routing

📝 Commits (5)

  • 7e57b1e Refactor Blinko blueprint configuration and environment handling
  • 39d44ae Standardize tag formatting in meta.json
  • 086b682 Merge branch 'main' into fix/blinko-default-port-routing
  • 80cab4d FIX-Validating meta.json against blueprint folders and logos
  • 3ce39ef Merge branch 'main' into fix/blinko-default-port-routing

📊 Changes

3 files changed (+17 additions, -46 deletions)

View changed files

📝 blueprints/blinko/docker-compose.yml (+7 -16)
📝 blueprints/blinko/template.toml (+10 -10)
➖ blueprints/blinko/template.yml (+0 -20)

📄 Description

What is this PR about?

New PR of Blinko Template

This PR refactors the Blinko blueprint configuration and environment handling to ensure the app is accessible via the assigned domain without requiring a manual port specification (:1111). It aligns the template with Dokploy’s expected routing behavior and simplifies environment variable usage.

Checklist

Before submitting this PR, please make sure that:

  • I have read the suggestions in the README.md file Dokploy/templates README
  • 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.

Issues related (if applicable)

closes #182

🔄 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/255 **Author:** [@jaainil](https://github.com/jaainil) **Created:** 7/31/2025 **Status:** ✅ Merged **Merged:** 8/2/2025 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `main` ← **Head:** `fix/blinko-default-port-routing` --- ### 📝 Commits (5) - [`7e57b1e`](https://github.com/Dokploy/templates/commit/7e57b1e0db6e99c2eace4386a30e797786ad2ce7) Refactor Blinko blueprint configuration and environment handling - [`39d44ae`](https://github.com/Dokploy/templates/commit/39d44ae8c8c591037de195adca25bfa286dcba24) Standardize tag formatting in meta.json - [`086b682`](https://github.com/Dokploy/templates/commit/086b6829debc4f3b16a7d46760520630fff625d0) Merge branch 'main' into fix/blinko-default-port-routing - [`80cab4d`](https://github.com/Dokploy/templates/commit/80cab4d57aeeb6b392640d22811a6efeff2172f6) FIX-Validating meta.json against blueprint folders and logos - [`3ce39ef`](https://github.com/Dokploy/templates/commit/3ce39ef142df66592a8d6788972d5188a39a2883) Merge branch 'main' into fix/blinko-default-port-routing ### 📊 Changes **3 files changed** (+17 additions, -46 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/blinko/docker-compose.yml` (+7 -16) 📝 `blueprints/blinko/template.toml` (+10 -10) ➖ `blueprints/blinko/template.yml` (+0 -20) </details> ### 📄 Description ## What is this PR about? New PR of Blinko Template This PR refactors the Blinko blueprint configuration and environment handling to ensure the app is accessible via the assigned domain without requiring a manual port specification (`:1111`). It aligns the template with Dokploy’s expected routing behavior and simplifies environment variable usage. ## 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) - [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 #182 --- <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:01 -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#314
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?