The Entire Site backup option is a welcome addition to this module. However, I am unclear why default/settings.php is listed in the files that are excluded from this backup. The settings file is often customised, so if I need to recover a site from this backup, I would expect this file to be part of it - and it would be a nasty shock to find it missing.
I imagine there are good reasons why it is excluded, but I suggest that this could be made more clear in the instructions and/or UI. For example, a help line below the list of excluded files/directories stating something like:
The default/settings.php file is one of the files that is excluded from an Entire Site backup. You should remove it from this list if you want to include it in your entire site backup.
Even better would be to remove it from the list, but add a checkbox to allow the user to specify whether to include that file in the backup or not.
Comments
Comment #1
Anonymous (not verified) CreditAttribution: Anonymous commentedwhy is it excluded?
Comment #2
panafff CreditAttribution: panafff commentedI am totally agree, this is a bad practice.
Comment #3
damban CreditAttribution: damban commentedAgree.
I can manually zip and download public_html to my PC and it includes settings.php
If I use this module to do a full backup, it is excluded.
Just imagine you didn't know that, and made a mistake, deleted, and reinstalled from the -ahem- "backup".
Only to find settings.php is missing an gone forever.
Comment #4
ecupaio CreditAttribution: ecupaio commentedOooh! I just did that. Now onto trying to recover my SQL db password
Comment #5
one_hoopy_frood CreditAttribution: one_hoopy_frood commentedI'm on:
7.x-3.1+11-dev
And this is still the default setting to not include default settings.php in the backup.
What was the rationale for doing this? Is there a use-case in which storing the default settings.php file would be bad?
Comment #6
couturier CreditAttribution: couturier as a volunteer commentedCan you verify if this is still an issue with the newest 7.x-3.2 release?
Comment #7
crystalgrafix CreditAttribution: crystalgrafix commentedI can confirm that this issue still exists with the .newest 7.x-3.2 release
Comment #8
DamienMcKennaThis is a bug from the POV that this file exclusion is never documented anywhere, sites could run into problems if this file wasn't backed up.
Ideally it should be managed by a setting.
Comment #9
dkronholm CreditAttribution: dkronholm commentedStill an issue apparantly. Just restored and found all sites to miss settings.php. Thank god for secondary backups :)
Comment #10
BrankoC CreditAttribution: BrankoC as a volunteer commentedI have been trying to find out, but this functionality seems to have sprung fully grown from the head of Zeus when the file 'includes/destinations.archivesource.inc' was added (which later became 'includes/sources.archivesource.inc').
I don't know what would happen if you restored into an existing installation (which seems to be the default restoration method). Would the settings.php be overwritten? Often that file is write-protected; what would happen then?
The module can also be used for migration; presumably you wouldn't want to overwrite the original DB (which might happen if you managed to restore settings.php).
Comment #11
solideogloria CreditAttribution: solideogloria commentedI would assume it's excluded for the same reason it should be excluded from git repositories.
Comment #12
BrankoC CreditAttribution: BrankoC as a volunteer commentedGood point. That reason is presumably security, because you end up storing login data (for the production database server) in lots of back-ups.
Comment #13
solideogloria CreditAttribution: solideogloria commentedShall we close this as "works as designed"?
Comment #14
DamienMcKennaLet's make this a feature request to allow controlling the files/directories which are normally excluded.