To create new platforms I've been using Drush make first, and creating the platform in Aegir second as described here http://omega8.cc/how-to-add-custom-platform-properly-140.

To use Drush make I have had to sudo su o1.ftp before Drush make will work - trying to use drush make as any other user has been giving me warnings that say something like "drush command could not be found" and "drupal installation directory could not be found. Drush make as user o1.ftp works.

Migrating sites to a new platform built this way works, but there's a warning message for each site that gets migrated: "Could not change permissions of /data/disk/o1/static/basefinal3/sites/all to 751 (chmod to 751 failed on /data/disk/o1/static/basefinal3/sites/all)".

If I chown -R o1 theplatformname while chmod-ing the platform and sites directories (before adding it to Aegir) I don't get those warnings when migrating sites to that new platform. This step doesn't fix anything (nothing's broken) but it does make the warnings go away, which seems much more proper. I can't chown it as o1.ftp, only as root.

I wonder if this new step in my process should be added to the documentation ...or maybe there's something wrong in my system?

Anyways, Thanks for the amazing BOA!

Comments

omega8cc’s picture

Status: Active » Fixed

These tasks didn't fail, of course. The warnings you see are not errors, and are safe to ignore.

Also, these not harmful warnings were always logged in custom platforms, just unnoticed, because previously Aegir didn't mark any task with that yellow icon if there were any warnings in the task log, but now it does, as explained in this thread: #1929372: Flag tasks with logged warnings

These directories are expected to be owned by Aegir system user and not your FTP/SSH user nor restricted only for the web server user, hence the warning, but the system will fix the ownership and permissions there every morning.

However, since this feature already caused a **ton** of noise in our own support queue with a tiny or none benefit, we have removed/reverted it in the Aegir fork used in BOA

Status: Fixed » Closed (fixed)

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