Having this weird issue where if I run my Django app in a systemd managed service, it can’t make any outbound networking calls (no DNS resolution, no opening of sockets), but when I run it manually, no problems. I’m not sure where to start looking. #uwsgi #systemd #django #network

New blogpost: https://blog.tyk.nu/blog/the-story-of-postgresql-choking-on-an-unreadable-home/

It is a lovely story about debugging TLS connection issues from Django to PostgreSQL.

The root cause turned out to be libpq erroring out when running with the environment variable $HOME set to an existing but unreadable path, in this case "/root"

Enjoy!

#django #postgresql #supervisor #uwsgi

The Story of PostgreSQL Choking on an Unreadable $HOME - TykBlog

Tyklings blog

#mood
Wed Mar 12 21:07:14 2025 - waiting for Emperor death...

#uwsgi

DjangoとuWSGI、Nginxの関係を理解したい - Qiita

はじめにDjangoを使ったアプリをデプロイする時にuWSGIとNginxが必要らしいと聞いて、役割や関係を理解するのに時間がかかったので書いておきますここでは、DjangoとuWSGI、Ngi…

Qiita

Since I have a single script using the #Python #cgi module (the rest is C++ using SimpleCGI), I figured that switching to a full framework was overkill. So instead I am rewriting using urllib.parse.parse_qs for the query string and email.parser for the multipart body.

Thanks for all the helpful comments! I found #uwsgi to be very useful for other parts of the code.

@jaseg That was indeed quite minimal. I struggled with the #uwsgi manual and was unable to find a definition for the application interface, but got some help from

https://dev.to/cwprogram/python-deployment-wsgi-with-uwsgi-d45

I have successfully converted the simple scripts, but I have one more complex one that need to handle POST data (both multipart/form-data, possibly some query parameters in the URI, and a direct binary POST with a file upload). The #cgi package did help me there, but I am struggling to find any documentation on how uwsgi handles that.

#Python

Python Deployment: WSGI with uWsgi

Installation The Somewhat Basics Configuration Notable HTTP Features Chunked Input...

DEV Community
#uspol but as #uwsgi status messages
Exploding memory usage in Django/uwsgi containers

We recently came across an interesting problem at work while migrating from one flavor of Kubernetes to another. It’s sufficiently obscure to merit a brief write-up for reference.

xahteiwi.eu
changelog | alwaysdata

Today is the day where we officially switched to using #uWSGI instead of #Gunicorn.

After a bunch of read&try&fail&loop, it seems we have a decent uWGSI configuration that is properly managed by our custom #OpenBSD rc.d file. There shouldn’t be any service outage as uwsgi has been running via tmux for 2 weeks now :)

It seems uWSGI uses less memory that Gunicorn. And it provides information regarding Bot detection.