Aegir does not utilize the settings.php in the same fashion as a standard drupal site. It requires the use of drush to determine site credentials. As such, the tarball created by the backup task cannot be used to move a site from an aegir host to a non-aegir host without admin manipulation.

Request the creation of an export task that produces a tarball of a site and that includes a settings.php file which conforms to a standard drupal installation.

CommentFileSizeAuthor
#4 provision-export.patch2.33 KBmig5
#3 provision-export.patch1.76 KBmig5

Comments

acy76’s picture

acy76 commented

I'd like to second the call for an aegir to non-aegir host export feature. Failing this, some documentation of the procedure (to be followed and implemented manually) would also suffice - I haven't seen any other discussion of the subject.

adrian’s picture

adrian commented
Status: Active » Needs work

committed a partial fix so you can ddd the following to ~/.drushrc.php file to disable the cloaked credentials :

$options['provision_db_cloaking'] = FALSE;
Anonymous’s picture

Anonymous (not verified) commented
Status: Needs work » Needs review
StatusFileSize
new provision-export.patch1.76 KB

Is this too insecure, temporarily replacing the settings.php for the site prior to generating a backup? (i'm not honestly sure of my own opinion of it)

Backend-only patch for now. Run as 'drush @yoursite provision-export'

Anonymous’s picture

Anonymous (not verified) commented
StatusFileSize
new provision-export.patch2.33 KB

Better patch that checks to see if the site already has unclocked credentnials as per #2 (and if so, just run a normal backup)

Anonymous’s picture

Anonymous (not verified) commented

How do we feel about the backup task *always* saving the site's settings.php with their unmasked credentials.

That way any backup can be used on a non-aegir host.

And it's ok to restore from such a backup because the restore task invokes verify, which would re-mask the settings.php (if $options['provision_db_cloaking'] = FALSE of course).

Thoughts?

Anonymous’s picture

Anonymous (not verified) commented
Status: Needs review » Fixed

Pushed the idea of #5 to HEAD. backups save the settings.php with uncloaked credentials so they can be used on non-aegir hosts. no extra provision-export task.

Anonymous’s picture

Anonymous (not verified) commented

This is a migression and should be reverted, see #955184: Backup task breaks any site by replacing settings.php with version working only with Apache

I'm just gonna leave this ticket closed because the new discussion is happening over there and we don't need two tickets.

Anonymous’s picture

Anonymous (not verified) commented
Title: Create export task which produces tarball which can be used to move site to non-aegir host » Save settings.php with uncloaked credentials on backup (for using on non-aegir hosts)

Renaming this to what was actually done, for the release notes at least.

j2parker’s picture

j2parker commented
Status: Fixed » Needs review

Regarding comment #2, The file ~/.drushrc.php does not exist. Are you suggesting this should be added to a site specific drushrc.php?

Is the following the answer to this feature request?

1. Hack drushrc.php per comment #2
2 .Verify the site
3. Backup the site

Anonymous’s picture

Anonymous (not verified) commented
Status: Needs review » Fixed

Yes you put that in the site's drushrc.php.

But this got committed and is in alpha15. Backups store the version of settings.php with uncloaked credentials, always. So I don't know why you need to reopen this (and mark it 'for review' without a patch either) .

You would only put that option in the drushrc.php of a site if you actually didn't want its *live* settings.php file to be cloaked (irrespective of backups)

Status: Fixed » Closed (fixed)

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