-
Notifications
You must be signed in to change notification settings - Fork 464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SMTP setup via env variables or encrypted config? #113
Comments
Hi @nebulade i think it would be best to have users configure SMTP via the settings UI instead of the ENV variables to make the installation process easier for everyone. There is only one required ENV variable - SECRET_KEY_BASE (rails encryption key). DATABASE_URL can be used to point the app to PG database - but if not specified it will run in an Sqlite DB. Let me know if that makes sense or if you need SMTP via env for some particular reason |
UPDATE: When SMTP is configured via ENV the smtp settings UI is still displayed - but the form is empty and those values are not copied into DB (which is probably good for the users). I've just added a commit to hide smtp settings from the UI when env variables are used. |
Thanks for the fast response! Great to have that change then and thanks for the clarification on how it works. And yes in Cloudron the SMTP settings are provided by the platform into the app to avoid having the user to configure those for each app, so with your change this will work very well. Besides that, there is still some things for me to work out on how to set this up. Sending an email results in the following resolving issue, but this may just be a quirk in Cloudron then. I am not a rails expert, so have to read up.
|
https://git.cloudron.io/cloudron/docuseal-app/-/blob/main/start.sh?ref_type=heads#L8 @nebulade based on the start.sh file it seems like you pass FROM address (email) into the SMTP_ADDRESS docuseal env variable - this variable should contain a DNS name of the host or IP address of the SMTP server (that's why you receive getaddrinfo: Name or service not know error) Replacing it with CLOUDRON_MAIL_SMTP_SERVER should fix the error |
Ah thanks for the second pair of eyes. I've set now the correct env variable with email sending success and can confirm that the email settings view is also neatly disabled if env vars are set. Looks like I can release a Cloudron package for our users then tomorrow. Great app! |
Thanks! appreciate your effort on making DocuSeal available on Cloudron
…On Sep 24 2023, at 11:00 pm, Johannes Zellner ***@***.***> wrote:
Ah thanks for the second pair of eyes. I've set now the correct env variable with email sending success and can confirm that the email settings view is also neatly disabled if env vars are set. Looks like I can release a Cloudron package for our users then tomorrow. Great app!
—
Reply to this email directly, view it on GitHub (#113 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AAI7GLZUFWTXOCKO5W3EOPTX4CGMJANCNFSM6AAAAAA5E6MZE4).
You are receiving this because you commented.
|
Just for reference, the initial app package is now available for Cloudron users. Great app! |
Hi @nebulade the latest 1.6.2 version introduces a new dependency - redis-server, which should be installed here: |
Hi, I am looking into packaging docuseal for Cloudron and mostly it works, besides the email/smtp config. My first question here is around how docuseal picks configuration values.
The package code exports the relevant STMP settings via env variables: https://git.cloudron.io/cloudron/docuseal-app/-/blob/main/start.sh?ref_type=heads#L8
Those seem to be picked up but are not shown in the settings UI. I guess those are thus never put into the settings db (encrypted config), which as such is good, as they can then presumably be updated on app restart if the env varibales change.
Is my observation correct here and is there any way then to prohibit showing the mail settings in the config UI to ensure a user will not overwrite those?
The text was updated successfully, but these errors were encountered: