Repository navigation
Replies: 1 comment
|
Thanks for building and publishing this. Worth separating two things: the template is useful, and it is yours. The repo has a standing rule against vendor and self-promotional placement, so the answer on a docs entry is no. Not because the template looks wrong, but because a listed platform is one we are implicitly vouching for and obliged to keep working. We would not control the compose file, the image it pins, or when it drifts from a release, and the first person to hit a stale pin would come to us. The same answer went to a similar request earlier, so this is the rule applied evenly. The stable contract is the releases: every tag now carries linux amd64 and arm64 archives plus checksums, which is a better thing for a template to point at than a guess at the registry. Keep publishing your template and link it wherever you like. If we ever add a deployment-platforms page it will be a neutral list with an explicit "listed, not endorsed" rule, and I would rather build that deliberately than one request at a time. Genuinely useful to know Dokploy is where people find tools like this. Thanks for asking first. |
Uh oh!
There was an error while loading. Please reload this page.
I recently added a Dokploy Template for Calnode (Check Here) . This can be added to the documentation as an easy option for one-click deploys
All reactions