Permissions for new files under tempates_c/en_US created using 751 permission which does not allow write for group

Question

After templates_c and en_US files are removed/deleted, Civi will recreate new folders and files. (This is recommended when upgrading Civi). Running as Apache these folders/files are then re-created with Apache as owner and group along with a 751 permission

This creates other problems. Drush running as a different user (other than Apache) can be denied access. Changing owners via other commands can cause other failures - as only Apache as owner has write access.

If these permissions were set as 775 (or 771), the problem would not occur. Is there a reason why these are set to 751? Where is this permission defined when new folders and files are created? There are workarounds but but have other consequences that are not desirable. (Other SE postings suggest things like 777 permissions - also not good.)

Answer 1

I always # sudo -u apache drush [command] when running drush anyway. That way if drush creates new files or directories they JustWork(tm) in drupal.

Answer 2

If you getting the error: Uncaught PHP Exception Unable to write to the .../files/civicrm/templates_c directory.

You probably have used drush cache clear run under your user account and that created the temp files owned by the user running drush.

So you can do what the first answer says and "run drush as the webserver user". But, since the files are there, you have to change permissions.

Look at the location [.../sites/mysite/files/civicrm/templates_c] and after you find the "civicrm" folder at the top, just change ownership to Apache/nginx so the web server can read & write cached files.

then cache clear as Apache/nginx

sudo -u apache drush cr