Custom and "private" Dokploy templates

[EdyTheCow]

What problem will this feature address?

Currently the only way to take advantage of really useful features provided by Dokploy templates (template.toml) is by submitting one to the official templates repository. Which is fine, but those templates have to meet a certain standard and have somewhat useful use-case for others.

I believe there should be a way to create "private" templates for personal use. They are reusable with a ton of well thought out features such as "helpers" (https://github.com/Dokploy/templates?tab=readme-ov-file#helpers). It could be useful for personal projects when deploying to take advantage of "helpers" functionality.

Describe the solution you'd like

I am not too familiar with inner workings of Dokploy, but these are the alternatives of implementing I came up with:

1. Probably the easiest method is to add an option for a custom endpoint to templates (https://github.com/Dokploy/templates). That way it could be self hosted and directly connect to Dokploy's UI.

2. Allow deploying docker compose with template.toml directly from a git repo, similar to how it currently works but with template.toml support.

3. Ability to add "helpers" functions inside .env files.

I would personally prefer self hosting templates because all of functionality is already there and because of ease of use since it's just a click of a button inside Dockploy's UI.

Describe alternatives you've considered

There aren't any alternatives to "helpers" functions because this is a Dokploy templates specific feature.

Additional context

No response

Will you send a PR to implement it?

Maybe, need help

[kerimovok]

+1

[junet-1]

+1

[ghassenbenghorbal]

This is a highly requested feature and would be great to have implemented.

[M4rshe1]

+1 on variant two

[mistuttodos]

+1. I also envision the template.toml could be inside the repo, and dokploy would deploy that app using that toml.

This would make truly self-contained app settings per 'template' repo. Couple that with copier and a gh workflow and you have a 'one click' new app, with domain settings, services, ports, backups, etc.. bundled.

A workaround is to have a gh workflow that hits the Dokploy API but this is not declarative and it's easy to mess up.