Skip to content

Fix documenso template#478

Closed
HowWhat42 wants to merge 2 commits intoDokploy:canaryfrom
HowWhat42:main
Closed

Fix documenso template#478
HowWhat42 wants to merge 2 commits intoDokploy:canaryfrom
HowWhat42:main

Conversation

@HowWhat42
Copy link

Fix and update documenso template to use the last version of the image.
Add more env variables in docker-compose.yml to fix errors on email verification.
Updated the template.toml to match the new env variables required.

- Changed Docker Compose version to include service name for production.
- Updated documenso image to use the latest version.
- Added new environment variables for SMTP configuration and other services.
- Adjusted volume paths and default values for environment variables to improve flexibility and error handling.
- Enhanced template.toml with additional SMTP settings for better email configuration.
@github-actions
Copy link

github-actions bot commented Oct 25, 2025

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
templates ✅ Ready (View Log) Visit Preview cadc1eb

@Siumauricio
Copy link
Contributor

I'm getting this errors
Screenshot 2025-10-25 at 7 10 01 PM

@HowWhat42
Copy link
Author

@Siumauricio Have you set the NEXT_PRIVATE_SMTP_FROM_ADDRESS var in your env ?

@Siumauricio
Copy link
Contributor

no @HowWhat42, the current documenso template we have works fine without assigning any env var

@HowWhat42
Copy link
Author

@Siumauricio I can say by experience that using the current template caused me several errors and hours of searching/fixing.
First, SMTP errors on register and login, then S3 for API file upload and finally signing errors related to certificate.
You can check the documenso discord, I'm not the only one having problem with the template.

@Siumauricio Siumauricio changed the base branch from main to canary November 28, 2025 09:17
@Siumauricio
Copy link
Contributor

So? the current documenso template works fine without assigning S3 keys

@Siumauricio
Copy link
Contributor

Close due to inactivity

@Siumauricio Siumauricio closed this Jan 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants