github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-03-12 01:56:43 -05:00
Code Issues 155 Packages Projects Releases Wiki Activity

[PR #471] [MERGED] Adding BentoPDF blueprint template for Dokploy #480

New Issue
Closed
opened 2025-11-22 20:39:29 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-22 20:39:29 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/471
Author: @jaainil
Created: 10/23/2025
Status: ✅ Merged
Merged: 10/25/2025
Merged by: @Siumauricio

Base: main ← Head: adding-bentopdf

📝 Commits (1)

  • d77086f chore: add bun.lock to ensure consistent dependency versions

📊 Changes

6 files changed (+734 additions, -27 deletions)

View changed files

➕ app/bun.lock (+672 -0)
📝 app/package.json (+27 -27)
➕ blueprints/bentopdf/docker-compose.yml (+8 -0)
➕ blueprints/bentopdf/image.png (+0 -0)
➕ blueprints/bentopdf/template.toml (+9 -0)
📝 meta.json (+18 -0)

📄 Description

What is this PR about?

Adding BentoPDF blueprint template for Dokploy

This PR adds a new blueprint for BentoPDF, a lightweight PDF conversion microservice that exposes a simple HTTP API for generating PDFs. The blueprint includes:

  • docker-compose.yml: Configured with the official bentopdf/bentopdf-simple:latest image
  • template.toml: Domain configuration with automatic routing setup
  • meta.json: Complete metadata with service description, links, and tags

The blueprint follows Dokploy best practices with isolated deployments, proper Traefik integration, and no hardcoded port mappings or container names.

Checklist

Before submitting this PR, please make sure that:

Issues related (if applicable)

None

🔄 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/471 **Author:** [@jaainil](https://github.com/jaainil) **Created:** 10/23/2025 **Status:** ✅ Merged **Merged:** 10/25/2025 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `main` ← **Head:** `adding-bentopdf` --- ### 📝 Commits (1) - [`d77086f`](https://github.com/Dokploy/templates/commit/d77086fb4c4f06c921fb823fe89fc1f11279f56b) chore: add bun.lock to ensure consistent dependency versions ### 📊 Changes **6 files changed** (+734 additions, -27 deletions) <details> <summary>View changed files</summary> ➕ `app/bun.lock` (+672 -0) 📝 `app/package.json` (+27 -27) ➕ `blueprints/bentopdf/docker-compose.yml` (+8 -0) ➕ `blueprints/bentopdf/image.png` (+0 -0) ➕ `blueprints/bentopdf/template.toml` (+9 -0) 📝 `meta.json` (+18 -0) </details> ### 📄 Description ## What is this PR about? Adding BentoPDF blueprint template for Dokploy This PR adds a new blueprint for BentoPDF, a lightweight PDF conversion microservice that exposes a simple HTTP API for generating PDFs. The blueprint includes: - **docker-compose.yml**: Configured with the official `bentopdf/bentopdf-simple:latest` image - **template.toml**: Domain configuration with automatic routing setup - **meta.json**: Complete metadata with service description, links, and tags The blueprint follows Dokploy best practices with isolated deployments, proper Traefik integration, and no hardcoded port mappings or container names. ## Checklist Before submitting this PR, please make sure that: - [x] I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-suggestions-when-creating-a-template - [x] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong. - [x] I have added tests that demonstrate that my correction works or that my new feature works. ## Issues related (if applicable) None --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-22 20:39:29 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#480
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?