django-fluo-emails
Simple emails template system db-dased and optional email db backend.
Install
DB Templates
Add emails.apps.EmailsConfig into your INSTALLED_APPS
#!python
INSTALLED_APPS = [
...
"emails.apps.EmailsConfig",
...
]
Email backend
Set EMAIL_BACKEND to 'emails.backend.EmailBackend'
#!python
EMAIL_BACKEND = 'emails.backend.EmailBackend'
Now every email is archived on db.
Usage
#!python
from emails.models import EmailTemplate
template = EmailTemplate.objects.get(name="myemail")
email = template.send(to=["receiver@example.com"])
CHANGES
0.2.0
- drop python2 support
- support for django 1.10
Metadata
Release files for django-fluo-emails 0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_fluo_emails-0.3-py3-none-any.whl | Python 3 | none | any | Details for django_fluo_emails-0.3-py3-none-any.whl |
Release files / django_fluo_emails-0.3-py3-none-any.whl
| Download URL | django_fluo_emails-0.3-py3-none-any.whl |
|---|---|
| Size | 19.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d6d4b1fa78fc8e77067a9fef6c4e6feb53107cf6114ee0962425d7e0fe05b065
|
|
BLAKE2b-256 checksum How to use checksums |
fe40284a9abdc9c517a77bfbc7bdf2f1b2a2c6afe144074c67a648d19394be40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.4.2 requests/2.22.0 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.19.9 CPython/3.6.9
|
Security for django-fluo-emails 0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.