borgmatic is great for restoring the occasional accidentally deleted file or database, but it's not as streamlined for the use case of spinning up an entire replacement system from nothing in the case of catastrophic server loss. That's because in order to function, borgmatic needs a configuration file with a list of Borg repositories to restore from, databases to restore, credentials, etc.
As part of this work, design and implement a better, more streamlined workflow for bootstrapping the restore of backed up files and databases to a totally blank system. This could include approaches like: 1. Automatically storing borgmatic configuration in a canonical location in any backup archive such that it can be restored or used upon restore, 2. Automatically storing borgmatic database configuration along with each backed up database dump so as to facilitate restore, and/or 3. Implementing a new borgmatic action like borgmatic bootstrap to provide the user with an entry point to some of these features. Additionally, update the documentation and tests accordingly.
Backup and restore of container volumes, either explicitly configured volumes in borgmatic configuration's file or auto-discovered volumes from opted-in containers (those with relevant labels) or both. Support for both Docker and Podman.