Graham Dumpleton

Have a read of: * https://www.agiliq.com/blog/2017/12/configure-django-log-exceptions-production/ At the minimum, set Django DEBUG mode on to work out what the error is.

What I did the last time when I need this yet again was to do: ``` jq -n env > $HOME/.local/share/workshop/workshop-environment.yaml ``` Then used the following arguments to `ytt`: ```...

JSON is a subset of YAML. So: ``` {"a": "b"} ``` is actually valid YAML as well.

Okay, that may not be strictly true, but for what we are generating here it is good enough. * https://john-millikin.com/json-is-not-a-yaml-subset

There should be no noticeable difference in mod_wsgi versions. What is the actual mod_wsgi configuration you are using?

I can only suggest try adding: * https://modwsgi.readthedocs.io/en/master/user-guides/debugging-techniques.html#tracking-request-and-response so you can capture request/response from Python WSGI entry point level to confirm that requests do get there and you aren't seeing...

With your setup Django would be loaded the first time a request hits a daemon process. How do you have Django's caching framework setup? * https://docs.djangoproject.com/en/4.1/topics/cache/

Since you are using: ``` WSGIApplicationGroup %{GLOBAL} ``` This forces the use of the main Python interpreter context of any process thus making it like running command line Python. Each...

To get rid of some of noise due to Python unnecessarily being initialised in Apache child processes (different to daemon processes), add outside of all VirtualHost definitions. ``` WSGIRestrictEmbedded On...

Similar but not the same. The other one is for `git` fetch, not `http` fetch. So different parts of code and for different functionality in `vendir`.