Currently WingFlow creates an archive of the current files in the server before uploading the new files, but this defeats the purpose of server backups. WingFlow should instead prefer creating a backup and resort to creating an archive if backups are unavailable.
Side note: process should continue on both failures, --guard stops the process if both fail, --fail-fast stops the process if the backup fails. Maybe this should be part of the configuration?
Currently WingFlow creates an archive of the current files in the server before uploading the new files, but this defeats the purpose of server backups. WingFlow should instead prefer creating a backup and resort to creating an archive if backups are unavailable.
Side note: process should continue on both failures,
--guardstops the process if both fail,--fail-faststops the process if the backup fails. Maybe this should be part of the configuration?