UI updates require apache user to be owner

[izmeez]

Description of the bug

This is a followup to #6759

In our use case there are two users: one is www that is the owner of all folders and files in the webroot and another www-data that is the group and the apache daemon. The permissions are 775 for folders and 664 for files. This setup works fine for allowing UI installation of new modules, themes and layouts, avoiding interruption emanating from authorize.php requiring FTP credentials which is a no go. When new modules are installed they acquire the following ownership and permissions: i.e. www-data:www-data with 755 for folders and 644 for files.

Subsequently, when UI updates are attempted they fail immediately with the message:

Your server does not support updating modules, themes, and layouts from this interface. Instead, update modules, themes, and layouts by uploading the new versions directly to the server, as described in the handbook.

This message is also seen by simply going to: /admin/config/system/updates.

If the ownership of all folders and files in the webroot is changed to www-data:www-data then UI updates work and updated modules have folder permissions 755 and file permissions become 644.

There must be something in the update checking that is specifically requiring the Apache daemon to be the owner somewhere else not allowing the original ownership and permissions to even be tried.

Additional information

Add any other information that could help, such as:

• Backdrop CMS version: 1.29.2
• Web server and its version: Apache/2.4.62 (Debian)
• PHP version: 8.2.25
• Database sever (MySQL or MariaDB?) and its version: 8.0.30
• Operating System and its version:
• Browser(s) and their versions: Firefox

[izmeez]

I think what I have described is a DevOps issue not a Backdrop bug. It might better be a support question, if not out of scope. I'll try adjusting labels to reflect.