SvcHub by LimpidMo runs your background services from one module instead of one module per service. It starts Termux services and standalone binaries at boot, keeps them running, and gives you a WebUI to control them.
What it does
- Two kinds of service: Termux services, which run without the Termux app in the background (as the Termux user by default, or as root if you switch it on), and binary services.
- Each service has its own start command and an optional clean-up command that runs once after it stops.
- Start and stop rules: a scheduled stop window, screen on/off, and Wi-Fi based start/stop.
- Keep-alive patrol every 60 seconds by default (10 to 84600 seconds), restarting services marked to run, with log rotation.
- Optional commands to run at boot.
The WebUI
Chinese and English, with light and dark themes. It shows service status, lets you edit services and read their logs. You can open it from the KernelSU or APatch manager, or in any browser at http://127.0.0.1:5555 with a password (default admin, change it). The browser version can be installed as a PWA.
Installation
- Install the zip from your root manager's Modules page.
- The installer offers, with the volume keys, to mount its own
resolv.conffor services that have DNS problems. It's skipped by default. - Reboot. Upgrades keep your configuration and login sessions.
- Magisk has no in-manager WebUI, so use the browser address above.
Termux services need Termux and the packages they use (pkg install). Binaries are up to you: get them from a trusted source and make them executable. All scripts are POSIX sh. GPL-3.0; docs at limpidmo.github.io/SvcHub.