[GH-ISSUE #646] Dokployfile.yml Concept & Template Generator #12686

New Issue

GiteaMirror · 2026-06-15T12:35:06-05:00

GiteaMirror commented

2026-06-15 12:35:06 -05:00

Originally created by @dealenx on GitHub (Jan 11, 2026).
Original GitHub issue: https://github.com/Dokploy/templates/issues/646

Hey Dokploy team! 👋

My main goal is to make use of the functionality Templates in Dokploy are as simple and accessible as possible. Currently, the process of creating and sharing templates looks difficult in my opinion, so this slows down their distribution.

I wanted sharing the template to be as easy as linking to a GitHub repository

💡 The solution: Dokployfile.yml as an alternative to meta.json

I have developed the concept of a Dokployfile, which is a simple YAML manifest that lies in the repository next to your code. It works by analogy with package.json or Dockerfile: describes metadata, icons, and specifies the path to docker-compose and template.toml.

🛠 Live Generator
To demonstrate this, I built a tool that parses a Dokployfile from any public GitHub repository and instantly generates the Base64 data needed for Dokploy.

👉 Try the Live Generator here (This link generates a template from template)

👉 Template Example here

Example Dokployfile.yml:

version: "1"
meta:
  slug: "my-app"
  name: "My App"
  logo: "logo.svg" 
template:
  compose: "docker-compose.yml"
  config: "config.toml"

The concept is described in more detail in my repository: dealenx/Dokployfile.

Template view (Link):

Template Generator view (Link):

Originally created by @dealenx on GitHub (Jan 11, 2026). Original GitHub issue: https://github.com/Dokploy/templates/issues/646 Hey Dokploy team! 👋 My main goal is to make use of the functionality Templates in Dokploy are as simple and accessible as possible. Currently, the process of creating and sharing templates looks difficult in my opinion, so this slows down their distribution. I wanted sharing the template to be as easy as linking to a GitHub repository 💡 The solution: **Dokployfile.yml** as an alternative to meta.json I have developed the concept of a Dokployfile, which is a simple YAML manifest that lies in the repository next to your code. It works by analogy with package.json or Dockerfile: describes metadata, icons, and specifies the path to docker-compose and template.toml. 🛠 Live Generator To demonstrate this, I built a tool that parses a Dokployfile from any public GitHub repository and instantly generates the Base64 data needed for Dokploy. 👉 [Try the Live Generator here](https://dealenx.github.io/Dokployfile/dealenx/dokployfile-template-databasus) (This link generates a template from template) 👉 [Template Example here](https://github.com/dealenx/dokployfile-template-databasus ) Example Dokployfile.yml: ``` version: "1" meta: slug: "my-app" name: "My App" logo: "logo.svg" template: compose: "docker-compose.yml" config: "config.toml" ``` The concept is described in more detail in my repository: [dealenx/Dokployfile](https://github.com/dealenx/Dokployfile). Template view ([Link](https://dealenx.github.io/Dokployfile/dealenx/dokployfile-template-databasus)): <img width="805" height="637" alt="Image" src="https://github.com/user-attachments/assets/c78a6e15-6cb5-4d4d-ad5d-3db4db028244" /> Template Generator view ([Link](https://dealenx.github.io/Dokployfile/generate)): <img width="890" height="637" alt="Image" src="https://github.com/user-attachments/assets/43844893-4495-4430-b5bb-c4cc916cbfe2" />

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#12686

[GH-ISSUE #646] Dokployfile.yml Concept & Template Generator #12686

[GH-ISSUE #646] `Dokployfile.yml` Concept & Template Generator #12686