The thought occurred to me that I could knock out both issues #10 and #11 with Cloudflare Tunnel to make setting up production access over HTTPS fairly painless. After some experimentation I managed to add support for this without impacting the local development experience, and without needing to juggle any certificates.
Two new environment variables have been added to .env:
CLOUDFLARE_TUNNEL_TOKEN
PROD_HOST_NAME
These are commented-out to make production access opt-in. The README details instructions for configuring these values to get Django available in production at https://$PROD_HOST_NAME.
The thought occurred to me that I could knock out both issues #10 and #11 with Cloudflare Tunnel to make setting up production access over HTTPS fairly painless. After some experimentation I managed to add support for this without impacting the local development experience, and without needing to juggle any certificates.
Two new environment variables have been added to .env:
CLOUDFLARE_TUNNEL_TOKENPROD_HOST_NAMEThese are commented-out to make production access opt-in. The README details instructions for configuring these values to get Django available in production at
https://$PROD_HOST_NAME.