4 question for clarification, please: drush upgrading, and permissions problem - 111 vs 999.
1.) Is it best practice NOT to do a drush based upgrade of Octopus hosted sites from one minor version of Drupal to another?
I recently did this, and logged-in via SSH as the o1.ftp user could not upgrade from 7.18 to 7.19, with error message returned: "failure to successfully upgrade core " and "Could not write to drupal root". I checked my permissions and the install profile was set to 755, with the owner being 111 and the group being 100. I was able to upgrade to 7.19 by changing the permissions to 775, for some of the default install profiles, but NOT for any of my 7.18 static install profile sites.
When I tried to do the upgrade to 7.19 on the /static/ custom install profiles, drush returned a success message, but when I ran "mup" again, it told me that the update still needed to take place. Looking into the site itself, clearly no update had taken place, even though drush reported success.
I was only able to upgrade to 7.19 on the static, custom install profile sites by logging in as the root user and running "upc", which the first time falsely reported success again, but then when I ran "up", there was actual success in updating the install profile to 7.19.
My questions are the following: (I may not be posting this in the right place, but don't want to open a new issue if I am incorrectly using BOA):
a.) Should I NOT do these manual minor release updates to the drupal core at all, as this (http://drupal.org/node/1896748#comment-7073248) thead suggests?
b.) Do I run any risks to the install profiles and sites built on them by running drush commands as the root user?
2) I noticed that some of the install profiles and some sites had the permissions set to 111:100 (o1:aegir), and others had permissions set to 999:100 (o1.ftp:aegir). I imagine they should all be either one or the other. Which one is correct, please?
I am using BOA 2.0.5 with default everything, PHP 5.3 modern only, and no customizations. I HAVE run the xdrago script after the successful update to 2.0.5, and it has NOT fixed these problems with permissions and ownership.
Thank you.
Comments
As the documentation/best
As the documentation/best practise states, NEVER update core using drush if using Aegir, it's against the whole principle on which Aegir was built on.
Best practise is to create a new platform with an updated core and migrate your sites to it.
Many choose to maintain platform builds using makefiles so you can easily deploy a core change with a simple version number update within the makefile, the same applies for updating modules and themes.
You should NEVER have to alter permissions in a BOA environment.
You're likely to have broken the platform you've been working on and I suggest you create a fresh platform and migrate your sites to it.
All of this is in the BOA documentation and on the omega8.cc website.
Request confirmation of proper 111 vs 999 permissions, please.
Hello, thanks for your comment. In order to fix my BOA, I need to know whether the following directories need ownership set to o1 or o1.ftp (i.e. 111 or 999), please:
/data/disk/fast1/static/platforms/platform-name/sites/
/data/disk/fast1/static/platforms/platform-name/sites/all/
/data/disk/fast1/static/platforms/platform-name/sites/all/modules/
Thank you.
Well, I figured out that these ownerships must be set to 111:100 - it seems that that will work for me.