[GH-ISSUE #310] Feature Request: Develop an Open Web Application for Collaborative Template Management with Automated Version Control and Testing #15427

Closed
opened 2026-07-14 22:41:44 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @yogeshalon on GitHub (Aug 25, 2025).
Original GitHub issue: https://github.com/Dokploy/templates/issues/310

Maybe a Scheduler Inbuilt

Description:
We propose building an open-source web application that allows users to:

Upgrade or modify existing templates.
Create entirely new templates from scratch.

To ensure seamless collaboration and quality control:

Whenever a user makes a change to a template, the system will automatically create a new branch in the version control system (e.g., Git).
This branch will then trigger an automated process to pull the relevant container image (e.g., Docker image) and run tests on it.
If the tests pass successfully, the changes will be queued for manual approval (e.g., by maintainers or admins) before merging into the main branch.

This feature aims to foster community-driven improvements while maintaining reliability through automation and oversight.

Originally created by @yogeshalon on GitHub (Aug 25, 2025). Original GitHub issue: https://github.com/Dokploy/templates/issues/310 Maybe a Scheduler Inbuilt Description: We propose building an open-source web application that allows users to: Upgrade or modify existing templates. Create entirely new templates from scratch. To ensure seamless collaboration and quality control: Whenever a user makes a change to a template, the system will automatically create a new branch in the version control system (e.g., Git). This branch will then trigger an automated process to pull the relevant container image (e.g., Docker image) and run tests on it. If the tests pass successfully, the changes will be queued for manual approval (e.g., by maintainers or admins) before merging into the main branch. This feature aims to foster community-driven improvements while maintaining reliability through automation and oversight.
Author
Owner

@Siumauricio commented on GitHub (Jul 14, 2026):

The goals here are largely covered by the current workflow: every PR gets an automated preview deployment, templates are now deploy-tested against a live Dokploy instance before merging, metadata is per-template (#978) eliminating collaboration conflicts, and CI validates every blueprint. A separate collaborative web app with built-in scheduling isn't planned. Thanks for the detailed proposal!

<!-- gh-comment-id:4974120154 --> @Siumauricio commented on GitHub (Jul 14, 2026): The goals here are largely covered by the current workflow: every PR gets an automated preview deployment, templates are now deploy-tested against a live Dokploy instance before merging, metadata is per-template (#978) eliminating collaboration conflicts, and CI validates every blueprint. A separate collaborative web app with built-in scheduling isn't planned. Thanks for the detailed proposal!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#15427