Continuing the discussion from Cfx.re Community Pulse - September 2022 Edition:
Just asking why this was added to make it so we can’t modify it externally.
It is part of txAdmin’s core design principles that tx as a whole should be self contained.
One could see this by the fact that we even implemented in-process “database” through lowdb, instead of using an external one like MySQL.
Just like the database, the admins.json file should be controlled exclusively by txAdmin as it is the authority regarding it’s data, validation, and every bit of business logic related to it.
What happens if people start developing external tools to interface the tx config or data files? Suddenly we start having compatibility issues where people may refuse to update because their whatever tool is not compatible with it anymore.
If you need to modify the admins.json file externally, it’s usually because of lost account access, in which case we recommend you close txAdmin entirely, delete the file, then start txAdmin and let it rebuild it for you.
This change is only breaking in the sense if you try to start more than one txAdmin in the same txData folder (for instance multi servers) and use the admin manager with both servers on, but this was contemplated and decided not to be a strong enough argument to block this change, specially considering in the upcoming months we are planning on giving txAdmin multi-server capabilities, so admin syncing soon won’t even be a relevant issue anymore.
1 Like
Sorry for the loss but i think this should be release its a grate ui ! thanks