Let's Encrypt App for Django
django-letsencrypt will allow you to add, remove, and update any
ACME challenge objects you may
need through your Django admin interface. Simply add the ACME challenge
and response for your app to serve up the necessary information for
Let's Encrypt validation.
This project strives to make installation, configuration, and usage a snap! From high levels of code coverage, multiple compatible python versions, multiple versions of Django supported, even multiple databases too!
And of course all wrapped up and published to PyPI for standard installation!
Supported Configurations
django-letsencrypt is tested across a number of configurations, here's what's
supported so far:
- Python Versions Supported:
3.14(with Django6.0,5.2)3.13(with Django6.0,5.2)3.12(with Django6.0,5.2,4.2)3.11(with Django5.2,4.2)3.10(with Django5.2,4.2)
- Django Versions Supported:
6.0minimum version6.0.45.2 LTSminimum version5.2.134.2 LTSminimum version4.2.30
- Databases Supported:
mysqlpostgressqlite
Recent Build Status Badges
Installation & Configuration
-
pip install django-letsencrypt -
Add
letsencryptto yourINSTALLED_APPS
INSTALLED_APPS = [
... ,
'letsencrypt',
... ,
]
- Include the
letsencryptin your project'surls.py, or where applicable (usually your rooturls.py).
re_path(r'^\.well-known/', include('letsencrypt.urls'))
-
Run
manage.py migrateto create the required table for theletsencryptmodel -
Create your
ACME Challengeobjects in your Django admin interface -
Test your
ACME Challengeobjects and their responses by visiting them:
{Django Site}/.well-known/acme-challenge/challenge_text
- Enjoy your easy to manage
ACME Challengesinside your Django project!
Example Project
If you would like a demo of how to use this application simply clone this project's
git repository from GitHub,
take a moment to read the README.md file within the
example_project
directory, and follow the directions. That will spin up a small sample django
application already configured for you to try out.
Development
- Make sure you have installed uv in your environment.
- Clone the repo to your development machine.
- Configure your
githooks withgit config core.hooksPath .githooksfor the project. - Run
uv syncto create the virtual environment and install required dependencies. - Run
make testfor the full test suite. - Run
make test-toxto run the entiretoxsuite.
Metadata
Release files for django-letsencrypt 6.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django_letsencrypt-6.0.2.tar.gz | 14.0 kB | Without provenance | Details for django_letsencrypt-6.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_letsencrypt-6.0.2-py3-none-any.whl | Python 3 | none | any | Details for django_letsencrypt-6.0.2-py3-none-any.whl |
Total release size: 28.1 kB
Release files / django_letsencrypt-6.0.2.tar.gz
| Download URL | django_letsencrypt-6.0.2.tar.gz |
|---|---|
| Size | 14.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d79198e44f23ba894b40fbedbc7f7fc6eef4492a106ae7f5fb15b6b1b733d5ef
|
|
BLAKE2b-256 checksum How to use checksums |
4d43491e90ec7db15089eca97edc82f73b78ea489888715c0312f5e47e965e4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / django_letsencrypt-6.0.2-py3-none-any.whl
| Download URL | django_letsencrypt-6.0.2-py3-none-any.whl |
|---|---|
| Size | 14.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1a5f35b97145be898feb2502cbe5d001bd0d07d502ccf17d99ed7f27ea671265
|
|
BLAKE2b-256 checksum How to use checksums |
80a4ccf1a3d912a113db23b6823682510c5fa0c0810ceca23e422f38b146d4c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for django-letsencrypt 6.0.2
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.