You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the ability to take a backup is important and good enough as it is . But at the moment new features has being added to wled that is not covered by the current backup functionality . Ledmaps , json animation ..etc will all have to be manually backed up .
It would be nice if we can dump wled/edit content as one file for backup and then restore the same way . Not asking for an api to also do that but that would also be nice .
Just to clarify I am doing that purely to enhance wled and we do I not have any real life use case to backup that frequently ( well we do a lot of destructive tests and it will make our life a bit easier ) . If that is will not be considered then we could script it from our side so not the end of the world as the firmware backup script is a good example
The text was updated successfully, but these errors were encountered:
Until this is implemented in UI (perhaps not so easy) you can use a simple wled-ip/ledmap.json, wled-ip/2d-gap.json, etc to open and then save those files from a browser.
Yeah that is the way I backup now , I have a folder with each MCUs content . I was thinking to modify this script https://github.com/Aircoookie/WLED/blob/main/tools/multi-update.sh so instead of an update it will do download , so no worries you may close or keep as a reminder
I think the ability to take a backup is important and good enough as it is . But at the moment new features has being added to wled that is not covered by the current backup functionality . Ledmaps , json animation ..etc will all have to be manually backed up .
It would be nice if we can dump wled/edit content as one file for backup and then restore the same way . Not asking for an api to also do that but that would also be nice .
Just to clarify I am doing that purely to enhance wled and we do I not have any real life use case to backup that frequently ( well we do a lot of destructive tests and it will make our life a bit easier ) . If that is will not be considered then we could script it from our side so not the end of the world as the firmware backup script is a good example
The text was updated successfully, but these errors were encountered: