Need to add `--wsgi-env-behaviour holy` to wsgi conf

[hyanwong]

Otherwise we are getting this in the a.onezoom.org_uwsgi_stderr.log

Thu Aug 27 12:49:09 2026 - unable to set environ to the python application callable, consider using the holy env allocator

So we need to add --wsgi-env-behaviour holy on e.g. line 93 of install-supervisord.sh

Doe that sound OK @lentinj ?

[hyanwong]

ChatGPT says:

You're on 2.0.31, so you inherited the old cheat default. By explicitly specifying:
--wsgi-env-behaviour holy
you're effectively opting into the environment-allocation behaviour that newer uWSGI considers the normal/default approach.
So given that it fixes the errors, I'd leave that option enabled. There's little reason to prefer the old cheat optimization unless you've measured a meaningful performance benefit from it.

[lentinj]

Seems worth sucking and seeing at least, looking at the docs I'm guessing we're tripping over permissions being dropped root -> web2py than anything else.

Another option could be to get rid of the --uid & --gid options in uwsgi and use supervisord's user and group options as background_tasks does. I'd prefer the latter, but there's likely a reason I did it this way around. Possibly to ensure the socket can be created.

[hyanwong]

Aha, could be permissions. The web2py files are all user web2py, group web. The uwsgi process is (I think) running under user www. It could be that all I need to do is add the group web to the user www?

[hyanwong]

It appears to be this. I did sudo pw groupmod web -m www and the default config now appears to work

[hyanwong]

Gah, the permissions fix didn't actually work, so I think it would still be a good idea to add --wsgi-env-behaviour holy. I assume there are no significant performance issues associated with this.