[PR #217] [MERGED] Allow SMTP configuration via environment variables #915

Closed
opened 2026-02-25 23:44:07 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/healthchecks/healthchecks/pull/217
Author: @timfreund
Created: 2/1/2019
Status: Merged
Merged: 2/1/2019
Merged by: @cuu508

Base: masterHead: configure-smtp-with-environment


📝 Commits (1)

  • 415ec58 Allow SMTP configuration via environment variables

📊 Changes

2 files changed (+14 additions, -1 deletions)

View changed files

📝 README.md (+7 -1)
📝 hc/settings.py (+7 -0)

📄 Description

This change allows SMTP configuration via email, but users can still choose to configure the settings directly in local_settings.py

This is helpful for docker-compose workflows: we configure a local mailhog container for development and we use a mailgun account for production. The account settings for each are passed in via deployment specific environment files.

I'm open to suggestions for improving this PR. Thanks!


🔄 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/healthchecks/healthchecks/pull/217 **Author:** [@timfreund](https://github.com/timfreund) **Created:** 2/1/2019 **Status:** ✅ Merged **Merged:** 2/1/2019 **Merged by:** [@cuu508](https://github.com/cuu508) **Base:** `master` ← **Head:** `configure-smtp-with-environment` --- ### 📝 Commits (1) - [`415ec58`](https://github.com/healthchecks/healthchecks/commit/415ec58b9530a5619507da60a3dd272fd1daf1f8) Allow SMTP configuration via environment variables ### 📊 Changes **2 files changed** (+14 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+7 -1) 📝 `hc/settings.py` (+7 -0) </details> ### 📄 Description This change allows SMTP configuration via email, but users can still choose to configure the settings directly in local_settings.py This is helpful for docker-compose workflows: we configure a local mailhog container for development and we use a mailgun account for production. The account settings for each are passed in via deployment specific environment files. I'm open to suggestions for improving this PR. Thanks! --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-25 23:44:07 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/healthchecks#915
No description provided.