GitLab

point to directions on how to setup a server

move install instructions to provision to simplify the bootstrap process (we just need provision now

more precisely: we resolve the publish_path so it's not relative, using
realpath()

without this, relative would end up in the apache config, breaking
vhosts

I had to move the D7 private stuff out of the platform section,
otherwise files were created for the sites/all dir

Conflicts:
	platform/provision_drupal.drush.inc

reset the makefile back to fetching hostmaster from git now that 0.4alpha5 has been tagged and released

Conflicts:
	aegir.make

this fixes a regression introduced in d8554cf433ddb0b665e05b143a28fac429196535

remove directory_name as it is not required. does not fix the untarring issue with drushmake and these .tgz files

this fixes a regression introduced in d8554cf433ddb0b665e05b143a28fac429196535

create d7's private dirs even on non d7 sites, as well as set appropriate permissions on them, to account for the future potential of upgrading d6 > d7 sites

before this patch, redirection virtual hosts were created with a duplicate ServerName, which seems to be working, but is needlessly confusing

after this patch, the redirection vhosts are created only based on the aliases provided and not the site_url

this implies that to do generic redirections (e.g. for SSL) you may need to push your site_url in the aliases array. that has been done in SSL so that all hosts (ie. aliases and the site_url) are redirected to the site_url, which is not appropriate for regular vhosts (because it would mean a infinite redirection loop)

overwrite the port 80 config if redirection + ssl is enabled, regardless of whether or not the file already exists

if we don't do that, the file is never re-written once it's been written once: bad.

was missing the install_mail function, and the format of body was changed from string to array.

this is to avoid the possibility of Denial of Service attacks from the drupal admins: if someone were to create a symlink in files/ that would point to the parent sites/ directory, the recursive chmod that happen on verify would loop inifinitely (i saw one running for 1h)