Hi,
On Thu, 12 Mar 2026 14:24:23 +0100 "Alexandre Rossi" <[email protected]>
wrote:
> Is /usr/share/doc/uwsgi-core/README.Debian not enough?
No, it is not enough, a multiple things are missing.
First, the section "Initscript for running uWSGI daemon" has to be
dropped as it is misleading, especially when old init script doesn't
work:
/etc/init.d/uwsgi start
Starting uwsgi (via systemctl): uwsgi.serviceFailed to start
uwsgi.service: Unit uwsgi.service not found.
failed!
Second, socket's path was changed, thus enabling .socket unit is not
enough, as one need to change nginx's (in my case) config. The old
System-V init script for apps-enabled/cgi.ini sets:
/run/uwsgi/app/cgi/socket
Now it is created by .socket unit (and from apps-available) as:
/run/uwsgi/cgi.socket
This change for existing configs is not mentioned too.
Third, the old init script starts the app with default.ini, now it is
not included, thus some options can be missing now and it needs
inspection. It is not mentioned too.
Fourth, not as important, but why both units are enabled? Enabling
.socket unit must be enough, worst enabling .service unit can be
misleading, as stopping it will not be enough, as .socket unit will
start it again on socket access. Remove enabling .service from README.
And simplify that enable & start by "enable --now"
Last and IMO most important, the NEWS is missing, after upgrade all
previously configured uwsgi apps just do not start (uwsgi.service unit
is missing as you can see in first snippet). It was enabled by some
systemd's magic, and thus after upgrade (and restart) one can notice
this too late. That is not expected...
BTW, consider remove the /etc/uwsgi/apps-enabled directory from package
at all, it is not needed anymore...
regards
--
Slavko
https://www.slavino.sk
