I feel like I'm so close to the finish line, by not using mod-wsgi that was packaged by the distro, in this case Alpine, and instead use #mod_wsgi from #pip.

I don't get the segfault core dumped error anymore, which is a huge relief cos that was annoying to debug, but I can't serve my pages yet either. I got this error instead:

Truncated or oversized response headers received from daemon process 'localhost': /base/base/wsgi.py

My final boss in solving this #Django on #Alpine container thing is getting #Apache/#WSGI (mod_wsgi) working. My container runs Apache fine, I suppose, if I don't supply it any site config - but once I do (i.e. in /etc/apache2/conf.d), I'm getting Segmentation fault core dumped errors and reboots.

I'm assuming, as far as my config goes, I need to point python-home to where my #virtualenv is, in addition to python-path to where my Django site/app is (like I do on #Ubuntu since that does not enforce the use of venv yet). But that doesn't seem to be enough, so again, in addition to apache2, apache2-mod-wsgi, and apache2-utils (and perhaps musl-dev and gcc in runtime other than just during build), what am I missing?

@bluetea “Colophon Redux”

Back in 2008, I whipped up this site with two hundred line hack using a newly created web framework called web.py and a brand new google project, App Engine. From 2008 to today, that’s how #seldomlogical worked.

From the user perspective it looked like plain HTML pages being served. Behind the scenes, code read markdown and converted it to HTML.

❝ Every time my blog ran, a little bit of Aarons code would execute

This was prior to the various web frameworks for python we take for granted today. Web.py utilised WSGI and I chose googles new toy, GAE to run it.

#webpy / #python / #WSGI / #GAE / #aaronswartz / #AppEngine / <https://seldomlogical.com/redux.html>