A dedicated configuration file format should be supported. These files with a specific name, like .wpbackuprc.yaml, can then contain a set of settings allowing users to trigger backups without having to pass a host of command line options or having to go through the wizard for every repeated backup on the same instance.
For ease of use, the application should offer to create such a file, based on running a dedicated wizard (#11).
In order to avoid ambiguity, the reading of a configuration file (from the current working directory?) should be triggered by a command line flag: wp-backup -c [backup|restore] or wp-backup --config-file [backup-restore].
A dedicated configuration file format should be supported. These files with a specific name, like
.wpbackuprc.yaml, can then contain a set of settings allowing users to trigger backups without having to pass a host of command line options or having to go through the wizard for every repeated backup on the same instance.For ease of use, the application should offer to create such a file, based on running a dedicated wizard (#11).
In order to avoid ambiguity, the reading of a configuration file (from the current working directory?) should be triggered by a command line flag:
wp-backup -c [backup|restore]orwp-backup --config-file [backup-restore].Settings contained in this file should include:
php binarywhether to usephp-wrapper