Open Fluxxo opened 7 months ago
This will make existing external solutions for scheduled backups useless. These scripts rely on the behaviour of the current backup.php
.
Would it change it I renamed the savebackup.php back to backup.php and ported the backup.php feature into a renamed settings page? URL calls would remain the same and the default behaviour as well, while still extending current functionality.
I made some changes to the way backups work in openwb1.9:
1) The "Backup erstellen" menu is gone, instead leading to a configuration page 2) Users can now decide where they want the backup to be stored: (a) Locally under /var/www/html/openWB/backup or remotely on an FTP server. The page performs a check whether the FTP credentials are correct and the remote folder is accessible. 3) Added fields to configure FTP connection 4) Added flag whether a nightly backup should be performed 5) Added a flag whether to apply filename backup.tar.gz or openWBbackup$jahr-$monat-$tag-$hourofday-$minute.tar.gz. 6) Added a button to manually perform a backup into the desired destination. 7) Adjusted the nightly cronjob to perform the backup if configured. 8) Backup can still be triggered manually via HTTP, but the URL changed from backup.php to savebackup.php 9) savebackup.php will spit out curl error codes in case it cannot store the backup.