I'm new to Aegir, using FreeBSD 10 and apache24. I have just created my first platform with:
~/platforms #drush dl drupal
then created the platform node which appeared to Verfiy correctly. I then created a site with this platform and had two permission type problems:
- Apache24 Directive problem which I fixed manually by editing the vhost.d file for the site by adding the lines:
<Directory "/var/aegir/platforms/drupal-7.26"> Require all granted </Directory>
Please can I request an amendment for apache24 so these Directives are created in the vhosts files during the sites install process. Guidance on best practise with using the correct directives would be helpful.
- Path permissions problem. The new site would not load due to the apache24 error in this post title. As a quick fix I
#chmod -R 755 /platforms/drupal-7.26
which I'm sure leaves the back door open and all the careful work during the Verify task has been compromised. Please advise if there is a better quick fix and perhaps you can fix the problem long term. I guess the permissions will be related to apache24 security. I notice with my installation the permissions in the ~/hostmaster-6.x-2.0 directory are less stringent than in ~/platforms/drupal-7.26.
Comments
Comment #1
kerolar CreditAttribution: kerolar commentedUpdate to 1. above. The code will disappear if you Verify a site and similarly if you place in platform.d and then Verify your platform. On further research I have read about post.d in aegir apache config files and have created a file ~/config/server_master/apache/post.d/apache24.conf with the same directive as above, to confirm:
There's now no need to manually edit every new sites vhost.d file. Note: you will need to add these lines for every apache24 platform created. I still need to understand these apache24 Directives better, so any tips appreciated. It's a quick fix but hopefully apache24 will be recognised during install in a later release.
Comment #2
kerolar CreditAttribution: kerolar commentedBTW, I'm still struggling with part 2 above, the permissions?
Comment #3
helmo CreditAttribution: helmo commented1. is handled in #2155445: 403 Forbidden in Ubuntu Saucy
2. this is probably fixed by the latest code ...