HEYFORM TEMPLATE: Add SMTP Configuration to .env.example for Email Notifications #7

New Issue

2025-11-22T20:29:03-06:00

GiteaMirror commented

2025-11-22 20:29:03 -06:00

Originally created by @chris86tian on GitHub (Mar 3, 2025).

To Reproduce

Added SMTP configuration variables (SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASS, SMTP_FROM, SMTP_SECURE) to .env.example.
Updated the README (if applicable) to include SMTP setup instructions.
Why this is needed:
Without email notifications, Heyform lacks a crucial feature—sending submission confirmations or internal alerts. This PR ensures that users can easily configure SMTP without modifying the source code.

How to test:

Copy .env.example to .env.
Fill in valid SMTP credentials.
Restart Heyform.
Submit a form and verify email delivery.
Additional Notes:

This change does not alter default behavior but provides clear guidance on SMTP setup.
Future improvements could include a UI-based SMTP configuration.
Let me know if any additional adjustments are needed! 🚀

Current vs. Expected behavior

It is not possible to configure the SMTP server with the heyform template.

Provide environment information

Ubuntu 24.04.2 LTS (GNU/Linux 6.8.0-52-generic x86_64)
Dokploy 0.19
VPS: Hetzner

Which area(s) are affected? (Select all that apply)

Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

Yes

Originally created by @chris86tian on GitHub (Mar 3, 2025). ### To Reproduce Added SMTP configuration variables (SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASS, SMTP_FROM, SMTP_SECURE) to .env.example. Updated the README (if applicable) to include SMTP setup instructions. Why this is needed: Without email notifications, Heyform lacks a crucial feature—sending submission confirmations or internal alerts. This PR ensures that users can easily configure SMTP without modifying the source code. How to test: Copy .env.example to .env. Fill in valid SMTP credentials. Restart Heyform. Submit a form and verify email delivery. Additional Notes: This change does not alter default behavior but provides clear guidance on SMTP setup. Future improvements could include a UI-based SMTP configuration. Let me know if any additional adjustments are needed! 🚀 ### Current vs. Expected behavior It is not possible to configure the SMTP server with the heyform template. ### Provide environment information ```bash Ubuntu 24.04.2 LTS (GNU/Linux 6.8.0-52-generic x86_64) Dokploy 0.19 VPS: Hetzner ``` ### Which area(s) are affected? (Select all that apply) Application ### Are you deploying the applications where Dokploy is installed or on a remote server? Same server where Dokploy is installed ### Additional context _No response_ ### Will you send a PR to fix it? Yes

GiteaMirror added the bug label 2025-11-22 20:29:03 -06:00

GiteaMirror commented

2025-11-22 20:29:04 -06:00

@chris86tian commented on GitHub (Mar 4, 2025):

Sorry, my English is not the best. Here are the code to place in the environment template:

SMTP-Konfiguration für Heyform:
SMTP_FROM="HeyForm noreply@example.com"
SMTP_HOST="mailserver.com"
SMTP_PORT=587
SMTP_USER=noreply@example.com
SMTP_PASSWORD=

@chris86tian commented on GitHub (Mar 4, 2025): Sorry, my English is not the best. Here are the code to place in the environment template: SMTP-Konfiguration für Heyform: SMTP_FROM="HeyForm <noreply@example.com>" SMTP_HOST="mailserver.com" SMTP_PORT=587 SMTP_USER=noreply@example.com SMTP_PASSWORD=

GiteaMirror commented

2025-11-22 20:29:04 -06:00

@Siumauricio commented on GitHub (Mar 15, 2025):

Templates are managed here https://github.com/Dokploy/templates, so we can move the issue there

@Siumauricio commented on GitHub (Mar 15, 2025): Templates are managed here https://github.com/Dokploy/templates, so we can move the issue there