While we recommend to build custom platforms on command line, so you can control permissions and ownership, in fact Aegir and our own system maintenance scripts take care only about the ownership and permissions on the platform level sites/all and site level sites/foo.com, to make sure that everything there is group writable.

The problem is that Aegir nor our maintenance systems don't check/fix any permissions on the installation profile level, so they are basically left at their initial state, as after running Drush Make.

This obviously locks the write access there forever and for the Aegir system user only, which is not expected.

Comments

Title:Permissions are never set correctly nor fixed on the installation profile levelPermissions are never fixed on the installation profile level
Status:Active» Fixed

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.