Skip to content
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

Feedback/Feature request: More advanced web administration #257

Open
mdziczkowski opened this issue Dec 1, 2024 · 4 comments
Open

Feedback/Feature request: More advanced web administration #257

mdziczkowski opened this issue Dec 1, 2024 · 4 comments

Comments

@mdziczkowski
Copy link

mdziczkowski commented Dec 1, 2024

Hello. Could You please expand the web admin panel that it could cover all administrative features and configurations thrh a online web interface?

Thanks

@mjl-
Copy link
Owner

mjl- commented Dec 1, 2024

Which admin features/config options are you missing?

Some background: Mox cannot currently change anything that's in mox.conf at runtime. Propagating changes made to mox.conf requires a restart of mox. Config options in domains.conf can be changed at runtime (that filename is a misnomer, "dynamic.conf" would have been better, and that's what it is named internally). Anyway, making config options from mox.conf configurable through the admin web interface isn't easy at the moment. It would be good to have more config options configurable without config file, perhaps just by having mox write a new mox.conf and restarting itself. But there is a risk that a config change will be made that causes mox to not start up again. Would have to be careful about that.

@mdziczkowski
Copy link
Author

If I may propose, above could be solved for example in following way:

  1. store the configuration files in json format
  2. use (either/or):
  • api
  • REST, DOM, etc.
  1. if required (depending from used programming language) a code that would "watch" for and aplly any changes without need to restart if the daemon/server

Above could solve the mentioned by you problems 🙂

@mjl-
Copy link
Owner

mjl- commented Dec 4, 2024

The challenging part is not storing the config changes to file, or the api to make changes. It's more that some changes are harder to apply at runtime (e.g. changing on which IPs mox is listening; it would require shutting down some listeners and starting some new listeners). So I took the easy approach of just requiring a manual restart. But I see the value in being fully configurable from the admin interfaces (both cli and web).

@mdziczkowski
Copy link
Author

The good thing is that at latest some developers are caring that it becones better ^_^

It would be also a great thing if the admin interface could be alsi become improved from the visual side 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants