Skip to content

Extend the backup functionality to inculde files under wled-ip/edit #3212

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dosipod opened this issue May 22, 2023 · 4 comments · May be fixed by #4625
Open

Extend the backup functionality to inculde files under wled-ip/edit #3212

dosipod opened this issue May 22, 2023 · 4 comments · May be fixed by #4625

Comments

@dosipod
Copy link
Contributor

dosipod commented May 22, 2023

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

@blazoncek
Copy link
Collaborator

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.

@dosipod
Copy link
Contributor Author

dosipod commented May 22, 2023

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

@dosipod
Copy link
Contributor Author

dosipod commented Jul 1, 2023

@blazoncek
Copy link
Collaborator

Indeed I have, but those are mine only as they are a bit involved.
Not yet ready for primetime.

Basicaly they are extensions of the update scripts.

@blazoncek blazoncek linked a pull request Apr 24, 2025 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants