Auto Config Backup enhancements
Backup Frequency is set to backup on change, changing/saving settings is delayed. This can range from only a slight but annoying delay to a longer inconvenient one resulting in a bad user experience. The backup logic should be improved with the following goals in mind:
- Page load times for saving changes (e.g. firewall aliases) should not be affected.
This could be accomplished, for example, by queuing backups to a service.
- Navigating to
Services / Auto Configuration Backupshould not be affected by internet connectivity.
Possible solution here is setting the landing page to
Updated by Christian McDonald 3 months ago
This is something that I've actually been looking into as well over the past few days in response to work on the WireGuard package. There is certainly improvements to be made here. Going back through the acb code, I found the -NoReMoTeBaCkUp override string that can disable acb on certain calls to write_config, which I'm now using and this does help...but backup on change is still a locking process in regards to the UI. I've honestly never recommended it, and have always recommended the more conservative schedule-based approach.
In addition to a service that can handle backing up in the background, do you think it would also make sense to bust acb out of pfSense proper and rebuild it as a package? Considering the work investment in building the service you're proposing, it might also be worth it to spend a little more time to convert acb to a package, that can then be maintained and updated separately...I've obviously been thinking about packages a lot over the last 2-3 months, so I'm quite partial to this more modular paradigm.