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

[PR #513] [MERGED] Fix(Documenso): Upgrade to v1.12.10 and add automatic signing certificate generation (fixes #1767) #514

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

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/513
Author: @Aj7Ay
Created: 11/7/2025
Status: ✅ Merged
Merged: 11/8/2025
Merged by: @Siumauricio

Base: main ← Head: main

📝 Commits (2)

  • eff5e93 Fix(Documenso): Upgrade to v1.12.10 and add automatic signing certificate generation (fixes #1767)
  • e133c92 Merge pull request #1 from Aj7Ay/fix/documenso-upgrade-and-signing-certificate-issue-1767

📊 Changes

1 file changed (+87 additions, -4 deletions)

View changed files

📝 blueprints/documenso/docker-compose.yml (+87 -4)

📄 Description

Fix(Documenso): Upgrade to v1.12.10 and add automatic signing certificate generation (fixes #1767)

Summary

This PR addresses the issue where Documenso deployments were stuck with a "Pending" status after both parties signed, as reported in GitHub Issue #1767. The root cause was identified as a missing or misconfigured signing certificate within the Documenso container's environment.

Changes

  • Upgraded Documenso image from v1.5.6-rc.2 to v1.12.10 (includes OpenSSL pre-installed)
  • Added automatic signing certificate generation in entrypoint script
  • Certificate generated at /app/certs/cert.p12 on container startup
  • Removed root user requirement (runs as user 1001 for security)
  • Uses pre-installed OpenSSL from v1.12.10 image
  • Added environment variables for certificate configuration with defaults
  • Resolves pending status issue after both parties sign

Testing

  • Tested locally with docker-compose up
  • Certificate generation verified working
  • All files created with correct permissions
  • Container runs without root privileges

Issues

🔄 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/513 **Author:** [@Aj7Ay](https://github.com/Aj7Ay) **Created:** 11/7/2025 **Status:** ✅ Merged **Merged:** 11/8/2025 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (2) - [`eff5e93`](https://github.com/Dokploy/templates/commit/eff5e937a14e17058ba957ab1f3c5ada1c474028) Fix(Documenso): Upgrade to v1.12.10 and add automatic signing certificate generation (fixes #1767) - [`e133c92`](https://github.com/Dokploy/templates/commit/e133c92dfb2993ed86281e0b7079641e818ad5e6) Merge pull request #1 from Aj7Ay/fix/documenso-upgrade-and-signing-certificate-issue-1767 ### 📊 Changes **1 file changed** (+87 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/documenso/docker-compose.yml` (+87 -4) </details> ### 📄 Description Fix(Documenso): Upgrade to v1.12.10 and add automatic signing certificate generation (fixes #1767) ## Summary This PR addresses the issue where Documenso deployments were stuck with a "Pending" status after both parties signed, as reported in [GitHub Issue #1767](https://github.com/documenso/documenso/issues/1767). The root cause was identified as a missing or misconfigured signing certificate within the Documenso container's environment. ## Changes - Upgraded Documenso image from v1.5.6-rc.2 to v1.12.10 (includes OpenSSL pre-installed) - Added automatic signing certificate generation in entrypoint script - Certificate generated at /app/certs/cert.p12 on container startup - Removed root user requirement (runs as user 1001 for security) - Uses pre-installed OpenSSL from v1.12.10 image - Added environment variables for certificate configuration with defaults - Resolves pending status issue after both parties sign ## Testing - Tested locally with docker-compose up - Certificate generation verified working - All files created with correct permissions - Container runs without root privileges ## Issues - Fixes [documenso/documenso#1767](https://github.com/documenso/documenso/issues/1767) --- <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:40:08 -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#514
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?