Question: Is headless/server-mode operation supported for the daemon? #231
Replies: 1 comment
|
I would also like to know if there are any plans to support web-based remote management — for example, a built-in lightweight web server that exposes a REST API or a web UI for adjusting fan speed, performance modes, and battery settings from a browser. This would be extremely useful for headless/server deployments. If not natively supported, does the daemon expose any IPC mechanism (D-Bus, socket, etc.) that could be used to build a custom web frontend? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi @PXDiv,
First of all, thank you for this great project!
I have a question regarding the daemon's operation. I noticed that the README mentions the daemon can run independently of the GUI and uses very low resources (~10MB RAM).
I would like to know if it is possible to run the daemon in a headless/server environment — that is, on a server edition of Linux without a graphical interface (no X11/Wayland), managed entirely via command line or configuration files.
Specifically, I have the following questions:
Does the daemon have a CLI interface or a configuration file that allows managing fan control, performance modes, and battery settings without the GUI?
Are there any plans to officially support a "headless" or "server" mode in the future?
If I install only the daemon (without the GUI), can it be controlled via D-Bus, socket, or any other IPC mechanism?
For context, I am exploring the possibility of using this on a Linux server environment (which happens to be PHN16-71). I understand this is not the primary use case, but the daemon's low resource footprint makes it intriguing for such scenarios.
Thank you in advance for your time and insight!
Best regards,
Emiya
All reactions