github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-07-16 04:48:50 -05:00
Code Issues 2.9k Packages Projects Releases Wiki Activity

[GH-ISSUE #519] Add validation for the template.toml file in CI #14488

New Issue
Closed
opened 2026-07-13 16:27:10 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-07-13 16:27:10 -05:00
Owner
Copy Link

Originally created by @Shrest4647 on GitHub (Nov 10, 2025).
Original GitHub issue: https://github.com/Dokploy/templates/issues/519

FYI: I am not good at toml.
During few of my pull requests, I have noticed this pattern of errors in which the problems in template.toml file syntax would pass undetected throughout my local test, and also the CI. I only notice it when fetching the template to run on a dokploy instance sometimes only after deploy. Although one could say it's a skill issue but I bet even seasoned developers would appreciate these fixes considering the convoluted toml syntax compared to yaml.

Some solutions for better experience:

  • Add a script for validating the template.toml file locally as well as on CI.
  • Add a detailed docs for the template.toml with multiple examples ranging from basic to advanced.
Originally created by @Shrest4647 on GitHub (Nov 10, 2025). Original GitHub issue: https://github.com/Dokploy/templates/issues/519 FYI: I am not good at toml. During few of my pull requests, I have noticed this pattern of errors in which the problems in `template.toml` file syntax would pass undetected throughout my local test, and also the CI. I only notice it when fetching the template to run on a dokploy instance sometimes only after deploy. Although one could say it's a skill issue but I bet even seasoned developers would appreciate these fixes considering the convoluted toml syntax compared to yaml. Some solutions for better experience: - Add a script for validating the template.toml file locally as well as on CI. - Add a detailed docs for the template.toml with multiple examples ranging from basic to advanced.
GiteaMirror commented 2026-07-13 16:27:11 -05:00
Author
Owner
Copy Link

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

This is implemented — the validate-docker-compose workflow validates every changed blueprint's template.toml (build-scripts/validate-template.ts) on each PR, and template metadata is now validated per-template via generate-meta.js --check (#978). Thanks!

<!-- gh-comment-id:4917204727 --> @Siumauricio commented on GitHub (Jul 8, 2026): This is implemented — the `validate-docker-compose` workflow validates every changed blueprint's `template.toml` (build-scripts/validate-template.ts) on each PR, and template metadata is now validated per-template via `generate-meta.js --check` (#978). Thanks!
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
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#14488
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?