You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Starman creates a UNIX socket it just inherits the prevailing umask setting, which often means that the socket is restricted so only the same UID can connect to it. It's common to deploy webapps as their own user ID, separate from the user ID the webserver is running as, so this is not ideal.
It would be useful if there was a configuration setting to chmod the socket; either. to mode 0777 and permit everything.
As an extra stretch-goal, a really nice configuration would be chmod to 0775 to permit the group and additionally supply a supplementary group that can be shared by the webserver, which can then be chgrp'ed onto the socket. E.g. platforms often use the group www-data for this purpose.
Thanks
The text was updated successfully, but these errors were encountered:
The OP probably knows how to do this but in case this helps anyone: I added these two lines to my Systemd service definition to handle the socket permissions:
When Starman creates a UNIX socket it just inherits the prevailing
umask
setting, which often means that the socket is restricted so only the same UID can connect to it. It's common to deploy webapps as their own user ID, separate from the user ID the webserver is running as, so this is not ideal.It would be useful if there was a configuration setting to
chmod
the socket; either. to mode0777
and permit everything.As an extra stretch-goal, a really nice configuration would be
chmod
to0775
to permit the group and additionally supply a supplementary group that can be shared by the webserver, which can then bechgrp
'ed onto the socket. E.g. platforms often use the groupwww-data
for this purpose.Thanks
The text was updated successfully, but these errors were encountered: