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.
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!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.tomlfile 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:
@Siumauricio commented on GitHub (Jul 8, 2026):
This is implemented — the
validate-docker-composeworkflow validates every changed blueprint'stemplate.toml(build-scripts/validate-template.ts) on each PR, and template metadata is now validated per-template viagenerate-meta.js --check(#978). Thanks!