With Django + Gunicorn + PostgreSQL + Caddy
- Try to build the
Dockerfilewithin the app directory, to see if everything's working fine. - If the app works, build a new compose stack using
docker compose up --build. - Try accessing in your browser to,
https://django.app.localhost/- Didn't work? That's great, it means your computer is still safe and is up to standards.
- You actually need to install a root certificate on to your computer's trust store just for this activity, and be sure to remove it later.
- From your browser settings, find a way to open a Trust Store manager.
- Import a new certificate which is at
caddy/data/caddy/pki/authorities/local/root.crt. - Try accessing the site again, it should get you there but might stuck on Not Found page.
- Navigating to admin page should work as usual.
Not much, but you get to test how your application runs on production and with HTTPS, so you are steps toward to more real-world production-like environment.
Doing this also enforces you to try the application with DEBUG=False, since you cannot really use development version of site to handle HTTPS requests.
Some OAuth2 providers also require HTTPS callbacks, so this way could be a good workaround to test something like so.
Additionally, here's why you'd always use HTTPS on production.
How about using this on your project development during this week before deployment?