Now we can run drush. But we can't upload modules and do other cool stuff in files/, let's do that too.

Comments

anarcat’s picture

anarcat commented

We'll probably need a "default" ACL here so that created files inherit the goods...

Do we want this optional? (I would say no.)

Do we want to recurse into existing directories? (I would say no.)

anarcat’s picture

anarcat commented
Status: Active » Fixed

done too, in head, the way i said.

omega8cc’s picture

omega8cc commented

I still didn't test it yet and only looked into code, so I will simply ask if something like this is expected to work as before in our Aegir SaaS setup:

* Aegir main admin/owner never has access to its aegir system user, so he can't operate in the hostmaster space/aliases at all.
* Instead, he is using separate account with restricted shell, and this account is a member of aegir group and www-data group.
* There are also other users (FTPS only) who can access only their sites/domain directories.

We are using default system umask 002 so the Aegir admin user can still access/overwrite changes made by other users in their sites.

The question is: should we simply add the same ACL for this admin users as now aegir user will have and the rest will work as-is?

anarcat’s picture

anarcat commented

the advantage of the provisionacl approach is that you get real site separation, without messing around with umasks, which grant *everyone* access to *every* site.

Status: Fixed » Closed (fixed)

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