Hello.
I suggest having the ability to roll back when an update has broken a configuration or a scene, for example.
A case that can happen is an automatic or manual update in the middle of winter that breaks its heating configuration. There is no easy way to roll back through the interface. The only way to do this is to delete the container to restart with the previous version, but you will have to do the same to return to the normal « v4 » installation and re-enable automatic updates.
I think this requires a change in the update process. Indeed, for Gladys to perform a backup before an automatic update, it must be Gladys that initiates the update. Maybe Watchtower sends a notification before an automatic update that we can retrieve to launch a backup.
Additionally, it is also necessary to indicate which version of the Docker image Gladys should install, which is not currently the case because the image tag is always « v4 ».
Finally, a backup of the database will need to be made, which will take some time and space on large installations.
I think this is a big project like local backup, but it’s an important feature.