I just started programming few custom addons and wanted to check if the addons folder is included in backup process or whether I should make the “addons” folder a repository and keep pushing the changes offsite.
Thanks for this report - I now see they are supposed to be backed up but they are not… I hope this bug will be resolved quickly.
The automatic backup system only creates one file. It does not create mutliple separate backup files. I.e. The single file that is created will have your addon backups in it.
This is about the /addons directory, which is the config for building custom addons/apps.
@petro , yes it creates a single tar file – which includes a number of gzipped files. The issue is the /addons folder is no longer being backed up. That folder contains the config for the local addons and used to be part of the stanard backups (see my first post). @RedKing , see the image above where Addons were selected in the backup.
I moved my custom addon onto another machine, and using a different approach to bring that addon’s data into HAOS to be included in my scheduled backups.
hmm, I wished this had ended up in a github issue or so. I found out the hard way that local addon source is not backed up, config is backed up, as well as the container. I’m able to restore and run the addon but the addons folder itself is empty after a full restore.
One ‘backup’ option is to host your addons/apps on github, then at least they are stored in a separate location.