[Request] Export/import option to backup and transfer settings/layouts

[ManCaveMedia]

The settings and layouts are saved to cache, so you don't have to create an account and save them each time you change them.
And I love that!

However, I would love to be able to export my settings (ie. to xml/csv/json/txt/etc.) and import them on a different device/browser.

But that's not the only use case...
I have a few layouts I switch between for practice, qualifying and races, but also mid-race to have a better view or view different teams/drivers. I noticed that when I save a layout and create a new layout from the exact same feeds (without closing and re-adding them), you can switch between these layouts without losing audio setup (language, volume, etc.). But after closing a feed and re-adding it, this won't work anymore. My guess is they get a unique id each time they're added. If I could export my layouts to a human readable format (ie. to xml/csv/json/txt/etc.) I could edit and copy over these id's and import these to do the fast layout shuffle mid-race without having to change audio settings and losing information. 😉

Does this make any sense?

[bootsie123]

Interesting! I'll add that as a feature, although I'll see if I can get it working without having to do that

[giantorth]

You could try adding a nosql database to save layouts on the server by username instead of putting in the browser cache.
It would be really helpful too if it detected someone had multiple layouts saved on login and let you pick instead of just loading the last used one.

[ManCaveMedia]

That would probably be a huge change, since it requires to setup a user registry and password management system too.

I don't mind the settings being stored locally, but since I put some time in tweaking my layouts (more time than setting up the docker 😉) it would be great if I can secure it by exporting/importing it. And the manual tweaks would be a bonus.

[bootsie123]

Definitely a really helpful feature, although it would have to be only available on the self hosted version. The idea with is to make the public website as static as possible so server hosting doesn't become an issue. If I end up going the server route for a more permanent fix for the CORS issue than it will definitely come to the public website