The config-editor on the admin panel currently just displays the config. The actual configuration changing process could be as follows:
User makes edits in config-editor
User clicks "Apply" button
Admin panel sends request with new config and mod name to an admin route (ex. "/admin/updateJMODConfig")
Jablko checks if the JSON is valid
Jablko then sets the config of the jmod (in Subprocess struct) and triggers a restart for that jmod.
To make sure users can troubleshoot invalid config settings, the output of each mod should be save in separate files using a rotating log system to control file sizes. In the admin panel, the outputs of each log could be viewed.
The config-editor on the admin panel currently just displays the config. The actual configuration changing process could be as follows:
To make sure users can troubleshoot invalid config settings, the output of each mod should be save in separate files using a rotating log system to control file sizes. In the admin panel, the outputs of each log could be viewed.