With the migration of lovelace from ui-lovelace.yaml to .stoarge/lovelace, I’m wondering if everything in .storage should be in my source control backups. Right I have the .storage directory excluded:
.gitignore:
.HA_VERSION
.storage/
.uuid
certbot/
home-assistant.log
home-assistant_v2.db
lets_encrypt/
Any best practices?
I would definitely backup .storage folder. I backup everything under /config
I wouldn’t worry about backing up the .db or .log, personally
Move it back to yaml and back that up. There is no Dev supported way to restore the storage registry post failure.
agree re: .db and .log
A snapshot isn’t a dev supported way? In any case, they tell you how to use raw edit mode and cut/paste - you could do the same thing to restore the .storage/lovelace
The challenge is the dev community has stated if you hand edit those files they will not support you. This is the ongoing saga on the zwave side of things as you can get into a place where you need to edit those files - and by doing so are in unsupported land.
So until the tools expand to allow editing and all the other needed functionality for the .storage backends I’d try to stick on yaml as long as possible.
Fair Call.
I’m actually maintaining the old YAML as well just in case I want to switch at some point. I just see the new storage lovelace as the future going forward and am going with it. The ‘supported’ method of switching to the new .storage/lovelace is cut/paste from YAML using the GUI anyway… I believe lovelace is the default soon anyway. It seems they are just making this up as they go along at the moment.