npm --prefix build-scripts run validate-template -- --dir ../blueprints/hedgedoc
npm --prefix build-scripts run validate-docker-compose -- --file ../blueprints/hedgedoc/docker-compose.yml
git diff --check
I have not live-imported this into a Dokploy instance yet, but the template passes the repository validators and keeps the compose file within the Dokploy template constraints.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/Dokploy/templates/pull/893
**Author:** [@autonomousventurelab-jpg](https://github.com/autonomousventurelab-jpg)
**Created:** 5/20/2026
**Status:** ✅ Merged
**Merged:** 7/7/2026
**Merged by:** [@Siumauricio](https://github.com/Siumauricio)
**Base:** `canary` ← **Head:** `avl/add-hedgedoc-template`
---
### 📝 Commits (2)
- [`a93faf4`](https://github.com/Dokploy/templates/commit/a93faf4101f2fca4d875caddfc911efd73859795) feat: add HedgeDoc template
- [`62e7d9a`](https://github.com/Dokploy/templates/commit/62e7d9a0f7c14548c27143853b938cba52bb2f37) Merge remote-tracking branch 'origin/canary' into avl/add-hedgedoc-template
### 📊 Changes
**4 files changed** (+104 additions, -0 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/hedgedoc/docker-compose.yml` (+37 -0)
➕ `blueprints/hedgedoc/hedgedoc.svg` (+32 -0)
➕ `blueprints/hedgedoc/template.toml` (+16 -0)
📝 `meta.json` (+19 -0)
</details>
### 📄 Description
/claim #152
## Summary
- Add a HedgeDoc template using the official `quay.io/hedgedoc/hedgedoc:1.10.8` image.
- Configure Postgres persistence, upload persistence, Dokploy domain routing, and generated credentials.
- Add the HedgeDoc logo and sorted `meta.json` entry.
## Validation
- `node build-scripts/process-meta.js`
- `npm --prefix build-scripts run validate-template -- --dir ../blueprints/hedgedoc`
- `npm --prefix build-scripts run validate-docker-compose -- --file ../blueprints/hedgedoc/docker-compose.yml`
- `git diff --check`
I have not live-imported this into a Dokploy instance yet, but the template passes the repository validators and keeps the compose file within the Dokploy template constraints.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
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.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/893
Author: @autonomousventurelab-jpg
Created: 5/20/2026
Status: ✅ Merged
Merged: 7/7/2026
Merged by: @Siumauricio
Base:
canary← Head:avl/add-hedgedoc-template📝 Commits (2)
a93faf4feat: add HedgeDoc template62e7d9aMerge remote-tracking branch 'origin/canary' into avl/add-hedgedoc-template📊 Changes
4 files changed (+104 additions, -0 deletions)
View changed files
➕
blueprints/hedgedoc/docker-compose.yml(+37 -0)➕
blueprints/hedgedoc/hedgedoc.svg(+32 -0)➕
blueprints/hedgedoc/template.toml(+16 -0)📝
meta.json(+19 -0)📄 Description
/claim #152
Summary
quay.io/hedgedoc/hedgedoc:1.10.8image.meta.jsonentry.Validation
node build-scripts/process-meta.jsnpm --prefix build-scripts run validate-template -- --dir ../blueprints/hedgedocnpm --prefix build-scripts run validate-docker-compose -- --file ../blueprints/hedgedoc/docker-compose.ymlgit diff --checkI have not live-imported this into a Dokploy instance yet, but the template passes the repository validators and keeps the compose file within the Dokploy template constraints.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.