ThomasB wrote: ↑18 Feb 2025, 03:46
The latest changes (that allow custom layouts) looks amazing. Hopefully you will be able to finish it before your March deadline. I can help test, but that is all.
- Thomas
Hey Thomas, i really appreciate your offer. I am almost finished but my code is usually like a rusty water pipe. Everytime i sealed a leak, it starts to leak somwhere else

Testing is very important as I cannot try every possible layout myself. So please feel free to play around with easyfetch.
My solution to store the settings for now:
On the "main" unit, easyfetch creates a file called "main_efc.json.gz" which contains all the information for each node.
In parallel, easyfetch stores an individual file called "efc.json.gz" on the remote node that has been customized. (So one can customize a node and deploy it as a standalone somewhere else.
The JS for the customization is loaded via CDN to keep easyfetch as small as possible. So internet is required for customizing the nodes
Now the thing
TD-er wrote: ↑14 Feb 2025, 18:41Pandora's box
Pandora's box has already been opened without anyone noticing.
I was so happy that my files were stored on the remote nodes, even with a CORS error. But so does a rules.txt. I don't think I need to explain what that means.
Edit: Unfortunately the fix to this issue will again take the easy out of easyfetch
