Hi all,
I would like to request a feature which would IMHO make a backup / restore / desaster case much easier to handle.
We know the state of a setupup once a user has downloaded and written an image.
How would it be if we could store all subsequent changes in the system in a form of a script which itself could be stored on a network mount, usb stick, etc.
That script could be something like: (Pseudocode)
== Start with base image
=== change IP to static 192.168.0.111 (etc)
=== install Wireguard Package
=== copy wireguard config etc…
==reboot
With something like that one only needs a cron to rebuild an replace such a script and when a desaster happens and the hardware needs to be replaced one uses the base image and then this script is applied.
What do you think? Would that be something doable?
Thanks a lot in advance. 
Personally, I don’t think a script like that makes much sense. Sure, you can track all the software that gets installed, but only if it’s done using DietPi’s own tools. But as soon as it comes to configuration, it’s nearly impossible to keep track of every change made to the system. You’d have to track every keystroke. Plus, there are plenty of software apps where configuration is done within the app via a UI. Add to that all the Debian package updates. It doesn’t really make sense, and over time it becomes more complex and takes longer. On top of that, the base image we provide changes over time, so you wouldn’t have an exact starting point if you needed an old image. A better and simpler solution is a complete system backup, such as the one we create with dietpi-backup. If you save it to an external storage device, you can load it directly during the first initial boot without any problems and won’t have to configure anything. This should be much faster than the script-based approach.